next-intl 2 pulls from a broken version of use-intl, Problem and Solution

[CescoIV]

Hello everyone,

While working on an older project running next-intl 2.14.6, I ran into the following issue:

./node_modules/next-intl/dist/src/react-server/index.js:8:0
Module not found: Package path ./dist/src/core is not exported from package use-intl

After some headaches and digging through my node_modules subfolders to check for exports; I saw that my yarn.lock file was pulling
use-intl@^2.14.6 which would resolve to use-intl v2.22.3 even after specifying v2.14.6 in package.json. The subdependency for next-intl was thus broken.

I added a resolution and a manual declaration of use-intl to my package.json to make sure next-intl didn't default to [email protected]

{
  "dependencies": {
    "use-intl": "2.14.6"
  },
  "resolutions": {
    "use-intl": "2.14.6"
  }
}

https://www.npmjs.com/package/use-intl/v/2.22.3?activeTab=readme

It looks like version 2.22.3 was a misnomer. It was unlisted in the version history in npmjs.com and I had to go to that url directly. I wanted to make this thread in case anyone else runs into this issue in the future, as it looks like older versions of next-intl 2 will automatically try and pull all the way up to v2.22.3 of use-intl.

Solution:
Adding the resolution field to my package.json, removing node_modules/yarn.lock/package.log/.next/etc, and reinstalling dependencies and building.

[amannn]

Somewhat interesting to me that yarn resolved to the deprecated version, it's the first time I've heard of this and there were a bunch of people von v2 when v3 was released.

Anyway, thank you very much for sharing this as a reference for everyone who's still on v2!