-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] npm install
installs the wrong things
#3606
Comments
We experience something similar when a package-lock is existing. This is only happening with npm 7.20.3.. earlier versions do not have this issue. Right now this is especially a problem on our CI pipeline, as we use the latest npm version there. We have a quite big monorepo in use with the workspace feature. |
This is the regarding debug log
|
This gets quite serious, have to explciity stick to npm 7.20.2 now. |
I figured that npm is dead / unmaintained. The last triaged issue is from the beginning of june. I just switched to yarn berry which is incredibly fast and works superb. Can recommend! |
I think the problem @simllll is describing is different. I have the same problem (original ticket description) with npm 7.20.2, 7.19, and 7.0.0. I've not tried npm 6.14.14 or earlier. Even with full nukes of |
we've made a lot of changes to peer dependency handling since this issue was opened. can any of you who are still experiencing this problem try installing [email protected] and let us know if it resolves your problem? |
@nlf Seems to work now using npm 8.7.0. I think this ticket can be closed. |
closing as we've received a report that things are working. if this is incorrect please feel free to either reopen this issue or open a new issue for us |
Hi, I have just encountered a very similar problem Environment
I get this error message from my console "Error: Expected constructor 2.0.0-rc.0:BundleGraph to be registered with serializer to deserialize" How do I solve this so I can get my app working again? |
I was receiving this error. It was not due to npm. It was due to having mismatched parcel dependencies. i.e. anything |
Is there an existing issue for this?
Current Behavior
When I install parcel parcel fails to run with this error:
Apparently the issue is
So parcel depends on a pinned package and npm is installing the wrong version.
Expected Behavior
NPM installs the right version and parcel works like it should.
Steps To Reproduce
@parcel/workers: Expected constructor 2.0.0-nightly.793+91287030:BundleGraph to be registered with serializer to deserialize
) parcel-bundler/parcel#6675@parcel/workers: Expected constructor 2.0.0-nightly.793+91287030:BundleGraph to be registered with serializer to deserialize
) parcel-bundler/parcel#6675npm install
andnpm run build
Environment
The text was updated successfully, but these errors were encountered: