Subpath files are not exported from packages anymore

[g0shed]

Bug report

After upgrading to the latest version of strapi I get the following error ehn trying to build

$ strapi build
✔ Compiling TS (1307.0721920728683ms)
⠋ Building build context
[INFO] Including the following ENV variables as part of the JS bundle:
    - ADMIN_PATH
    - STRAPI_ADMIN_BACKEND_URL
    - STRAPI_TELEMETRY_DISABLED
✔ Building build context (111.18539905548096ms)
⠋ Building admin panel
⠼ Building admin panel[ERROR] Module not found: Error: Package path ./admin/src/content-manager/utils is not exported from package <path>/node_modules/@strapi/admin (see exports field in <path>/node_modules/@strapi/admin/package.json)

Required System information

• Node.js version: 18.18.2
• NPM version: 9.8.1
• Strapi version: 4.15.2
• Database: mysql
• Operating system: Linux
• Is your project Javascript or Typescript: TypeScript

Expected behavior

Should be able to run stripe after upgrade

[deBasMan21]

I have the same issue here. All of a sudden it stopped working. No changes were made on my side. For me the module that cannot be found is ./admin/src/content-manager/hooks/usePluginsQueryParams. The rest of the error message is the same.

• Node.js version: 18.18.2
• NPM version: 9.8.1
• Strapi version: 4.15.4
• Database: mysql
• Operating system: MacOs
• Is your project Javascript or Typescript: Javascript

[ThewBear]

I think it's because of adding exports to the package.json file in this commit 0e69461#diff-d92ce1b3e295cd4b7db37a8b660078f2cca3e8b164fdba78a95b106774e94d6c which affects v4.15.2 and above.

From https://nodejs.org/api/packages.html#package-entry-points

Existing packages introducing the "exports" field will prevent consumers of the package from using any entry points that are not defined, including the package.json (e.g. require('your-package/package.json')). This will likely be a breaking change.

This broke my build since my code relies on getPaginationInfo from @strapi/strapi/dist/core-api/service/pagination. If the issue above is not fixed, Strapi should export getPaginationInfo function in the utils since this function is very useful when creating a paginated custom controller.

[AndColla]

Same issue here

• Node.js version: 18.9.1
• Yarn version: 1.22.19
• Strapi version: 4.15.4
• Database: postgres
• Operating system: Linux (Docker)
• Is your project Javascript or Typescript: Javascript

I get the error Module not found: Error: Package path ./admin/src/content-manager/utils is not exported from package /opt/app/node_modules/@strapi/admin

[derrickmehaffy]

duplicate: #18771

[g0shed]

@derrickmehaffy this is not a duplicate, and in the mentioned issue, it's stated that something that is breaking existing installations wont be fixed, how? why? if it's breaking either tell us a way to fix it or push a proper fix, simple

[derrickmehaffy]

@derrickmehaffy this is not a duplicate, and in the mentioned issue, it's stated that something that is breaking existing installations wont be fixed, how? why? if it's breaking either tell us a way to fix it or push a proper fix, simple

I don't agree with the decision myself but it was made above me. Best to discuss it on the main issue I linked but it is a duplicate.

[aviddv1]

@ThewBear I added

"./dist/core-api/service/pagination": { "types": "./dist/core-api/service/pagination.d.ts", "source": "./dist/core-api/service/pagination.js", "import": "./dist/core-api/service/pagination.mjs", "require": "./dist/core-api/service/pagination.js", "default": "./dist/core-api/service/pagination.js" },

to the exports in package.json in @strapi/strapi. Not ideal, but it's a temporary fix

Or, you could copy the contents of @strapi/strapi/dist/core-api/service/pagination.js locally instead of referencing the version in core

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/how-to-upgrade-from-strapi-v4-15-0-to-v-4-23-0/37545/2