Parcel doesn't work at all anymore (@parcel/workers: Expected constructor 2.0.0-nightly.793+91287030:BundleGraph to be registered with serializer to deserialize)
#6675
Comments
|
Same issue here, but in the original tickets "your environment" section it says |
|
Your example works for me. It looks like perhaps you have multiple copies of some node_modules somehow. Did you try cleaning out your node_modules or lock file and re-installing? |
|
I set up the folder in the .zip file from scratch - started with an empty folder, manually wrote package.json and ran I will download it again and see if the issue still happens and upload it for you with package-lock.json and node_modules folder. |
|
npm 7 indeed installs both a nightly and rc.0 version of some packages with {
"scripts": {
"build": "parcel build src/main.ts"
},
"devDependencies": {
"@parcel/transformer-sass": "nightly",
"parcel": "nightly"
}
} |
|
Thanks @mischnic 🥳 @devongovett it's still reproducable for me. Here's a whole folder: https://arxius.io/f/c4bf8eee |
|
Is it not a bug in npm? |
|
Ok. Wish my bug report good luck lol |
|
This might be "working as npm intended". It installs unsatisfied peerdeps as though they were regular dependencies now and RC does satisfy the alpha version peer dep constraint that some packages have: https://jubianchi.github.io/semver-check/#/^2.0.0-alpha.3/^2.0.0-rc.0 |
Thank you for making me realize npm is dead @devongovett. @folknor can you also imagine switching? |
|
I've been wanting to switch for a few years now, frankly. The only thing that held me back was I didn't want to spend the time doing the transition. But I believe that the time required to transition from npm to yarn berry is less than transitioning all my projects from parcel nightly to vite, so it's certainly looking attractive right now. I might give it a bit more time but not more than 1-3 weeks. |
|
Cool. I can recommend switching. For me it wasn't hard at all. I just removed node_modules and package-lock.json and ran this (parphrased) yarn set version berry command. Then |
|
Unfortunately It installs the correct ones when I do the initial |
|
@folknor I had that too. Make sure to delete |
|
This is still broken using npm 8.1.4. I retested because I was thinking perhaps it had been fixed by d4b4256 I've long since migrated all my projects to |
|
Thanks for the update @folknor!
Just an update from my side, I'm still on berry because I finally got the IDE situation somewhat sorted and am afraid to switch. The way I solved it was to write a script that does Did you report the issue to yarn / do you know if there is already an issue regarding this? |
|
@danieltroger I've not tested npm since my last comment. All my projects now run on pnpm and it works perfectly. As a side note, I enjoy the way pnpm handles npm obviously allows the same thing but has hundreds of copies of the same deps on the hdd by default, which pnpm by default doesn't. I did not report the issue to yarn, because at the moment I see no reason to use yarn over pnpm. #7489 probably fixed this for npm users. I ran a small test now using npm 8.3.0 and a clean copy (without node_modules, package locks, etc) of one of my projects, ran I think you should retest as well and close the ticket if it works for you. |
|
Thanks for the pnpm explanation! Clever to use links. But it's probably still slower than yarn, no? Since every file has to be on the filesystem.
Good point. Tested the reproduction and it works now 👌 |
That sounds like a reasonable assertion. I have no idea. Most of my projects are simple static websites with close to no dependencies except bootstrap and parcel, so speed is of no concern. |
|
This is happening again for me. Endless loop. The following repeats until aborted: Is the only solution then to use |
🐛 bug report
When trying to build a simple
console.log("test");on the nightly branch of parcel it infinite loops.🎛 Configuration (.babelrc, package.json, cli command)
package.json:
CLI command:
npm run build🤔 Expected Behavior
No infinite loop
😯 Current Behavior
💁 Possible Solution
Unsure
🔦 Context
Updated parcel this morning lusting for some fresh features and bugfixes and got this instead :(
💻 Code Sample
Please see this .zip:
parcel-fukd.zip
🌍 Your Environment
The text was updated successfully, but these errors were encountered: