Why do we get a different module federation build when you replace the package.lock with npm-shrinkwrap.json #26655
Unanswered
frontendplace
asked this question in
Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In our project we have in the .gitignore file the line "package-lock.json" and we switched to npm-shrinkwrap. When building or serving the remote and the shell, the module federation doesn't work. When removing the line in .gitignore and add a package-lock.json and remove the nmp-shrinkwrap everything works. We see that in the build folder a lot of files are also different.
I see in a commit: 67180d0 that shrinkwrap is not supported and there is dependency on yarn.lock, package.lock or pnpm-lock.yaml as package manager
Beta Was this translation helpful? Give feedback.
All reactions