Module not found: Error: Package path ./locale-data is not exported from package /node_modules/@formatjs/intl-displaynames (see exports field in @formatjs/intl-displaynames/package.json)

[alexeymolchan]

@formatjs/intl-displaynames: ^6.4.0,
react-intl: ^6.4.3,
typescript: ^5.1.3,
webpack: ^5.85.1"

tsconfig options:

"compilerOptions": { "module": "esnext", "moduleResolution": "node", }

https://formatjs.io/docs/polyfills/intl-displaynames#dynamic-import--capability-detection

after latest update dynamic loading of locale-data doesn't work.

the same error for @formatjs/intl-numberformat and @formatjs/intl-datetimeformat.

i suppose this is related to wildcard exports property in package.json.

"./locale-data/*": { "types": "./locale-data/*.d.ts", "default": "./locale-data/*.js" },
error thrown only when using dynamic import, import ar from "@formatjs/intl-displaynames/locale-data/ar"; works fine

[longlho]

please pin to the previous versions while we're investigating
cc @pyrocat101

[chenp1204]

The same error too,

[jlowcs]

With this in the package.json file, it seems to work for me:

    "./locale-data": {
      "default": "./locale-data"
    },

Also, adding this (with .js extension) for backward compatibility might be a good idea:

    "./locale-data/*.js": {
      "types": "./locale-data/*.d.ts",
      "default": "./locale-data/*.js"
    },

[webda2l]

Same with the latest release, about intl-listformat and my Component:

Import trace for requested module:
./components/_shared/_slice/PhilosophySlice.tsx
./pages/pricing/studio.tsx
- wait compiling /_error (client and server)...
- error ./components/_shared/FormattedList.tsx:39:8
Module not found: Package path ./locale-data is not exported from package /home/david/Works/OLYBe/website/node_modules/@formatjs/intl-listformat (see exports field in /home/david/Works/OLYBe/website/node_modules/@formatjs/intl-listformat/package.json)
  37 |   // Load the polyfill 1st BEFORE loading data
  38 |   await import('@formatjs/intl-listformat/polyfill-force')
> 39 |   await import(`@formatjs/intl-listformat/locale-data/${unsupportedLocale}`)
     |        ^
  40 | }
  41 | 

https://nextjs.org/docs/messages/module-not-found

import { shouldPolyfill as shouldPolyfillGetCanonicalLocales } from '@formatjs/intl-getcanonicallocales/should-polyfill'
import { IntlListFormatOptions } from '@formatjs/intl-listformat'
import { shouldPolyfill as shouldPolyfillListFormat } from '@formatjs/intl-listformat/should-polyfill'
import { shouldPolyfill as shouldPolyfillLocale } from '@formatjs/intl-locale/should-polyfill'
import React from 'react'
import { FormattedList as BaseFormattedList, useIntl } from 'react-intl'

type IProps = IntlListFormatOptions & {
  value: readonly React.ReactNode[]
}

export const FormattedList: React.FC<IProps> = (props) => {
  const { locale } = useIntl()

  if (!props.value) return null

  polyfill(locale)

  return <BaseFormattedList {...props} />
}

const polyfill = async (locale: string) => {
  // This platform already supports Intl.getCanonicalLocales
  if (shouldPolyfillGetCanonicalLocales()) {
    await import('@formatjs/intl-getcanonicallocales/polyfill')
  }
  // This platform already supports Intl.Locale
  if (shouldPolyfillLocale()) {
    await import('@formatjs/intl-locale/polyfill')
  }

  const unsupportedLocale = shouldPolyfillListFormat(locale)
  // This locale is supported
  if (!unsupportedLocale) {
    return
  }
  // Load the polyfill 1st BEFORE loading data
  await import('@formatjs/intl-listformat/polyfill-force')
  await import(`@formatjs/intl-listformat/locale-data/${unsupportedLocale}`)
}

No success with #4127 (comment)

No errors with:

        "@formatjs/intl-getcanonicallocales": "2.2.0",
        "@formatjs/intl-listformat": "7.2.2",
        "@formatjs/intl-locale": "3.3.0",
        "react-intl": "6.4.2",

[pyrocat101]

Sorry for breaking your build. The newer version should include the ESM export revert. See also: #4126 (comment)

[webda2l]

Sorry for breaking your build. The newer version should include the ESM export revert. See also: #4126 (comment)

No worries, thanks for your work.