- fix: resolve.exports wrong default @alexandrebodin
Full Changelog: v5.0.0-rc.18...v5.0.0-rc.19
Pre Release
Tag Name: v5.0.0-rc.19
Release Date: 9/9/2024
StrapiOpen-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.
Strapi v5.0.0-rc.19 fixes a critical issue with the resolve.exports default configuration that was causing module resolution problems. This release ensures proper module exports resolution, improving the stability of the CMS as it approaches the final v5.0.0 release.
resolve.exportsNo migration steps are required for this release. The fix for resolve.exports is applied automatically when upgrading to v5.0.0-rc.19.
It is highly recommended to upgrade to v5.0.0-rc.19 if you are currently using v5.0.0-rc.18 or any earlier release candidate of Strapi v5, especially if you are experiencing any module resolution issues. This release fixes a critical bug that could affect the stability of your Strapi application.
To upgrade:
npm install @strapi/[email protected]
or
yarn add @strapi/[email protected]
Fixed an issue where the default configuration for resolve.exports was incorrect, causing problems with module resolution. This fix ensures that Strapi properly resolves module exports according to the Node.js package exports specification, preventing potential errors when importing modules or packages that utilize the exports field in their package.json.
No new features were introduced in this release. This is a bug fix release focused on resolving an issue with the resolve.exports default configuration.
No security fixes were included in this release.
No specific performance improvements were included in this release. The focus was on fixing the module resolution issue.
This release addresses a specific bug related to module resolution in Strapi v5. The fix for resolve.exports default configuration ensures that Strapi correctly handles module exports according to the Node.js package exports specification. This improvement is particularly important for developers working with modern JavaScript modules and package structures.
While this change might seem minor, it resolves potential compatibility issues that could arise when using packages that rely on the exports field in their package.json. By fixing this issue, Strapi ensures better interoperability with the broader JavaScript ecosystem and provides a more stable development experience as the project moves closer to the final v5.0.0 release.
This release contains no breaking changes and should be a safe upgrade for anyone using previous v5 release candidates.
Full Changelog: v5.0.0-rc.18...v5.0.0-rc.19