You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
date-fns-tz (ESM) currently displays the below warning when being used with Webpack federated modules for micro-frontend architectures and requires a workaround which can hide some important Webpack warnings.
WARNING in shared module date-fns-tz
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file node_modules\date-fns-tz\dist\esm\package.json, or manually specify version in shared config.
In projects implementing federated modules Webpack requires the version to be present in nested package.json files. This allows Webpack to correctly resolve dependencies.
Webpack and NPM both determine that name and version should be required in all package.json files published publicly, including nested package.json files. See related issues below.
Related issue in Webpack: Issue 13457
Related discussion in NPM documentation: PR 134
I tested adding the name and version to package.json and the error was resolved.
Can we add this small change to enable users of federated modules, please? I am happy to add a PR for this.
The text was updated successfully, but these errors were encountered:
date-fns-tz
(ESM) currently displays the below warning when being used with Webpack federated modules for micro-frontend architectures and requires a workaround which can hide some important Webpack warnings.In projects implementing federated modules Webpack requires the version to be present in nested package.json files. This allows Webpack to correctly resolve dependencies.
Webpack and NPM both determine that name and version should be required in all package.json files published publicly, including nested package.json files. See related issues below.
Related issue in Webpack: Issue 13457
Related discussion in NPM documentation: PR 134
I tested adding the
name
andversion
to package.json and the error was resolved.Can we add this small change to enable users of federated modules, please? I am happy to add a PR for this.
The text was updated successfully, but these errors were encountered: