search

parcel-bundler / parcel

The zero configuration build tool for the web. 📦🚀
https://parceljs.org
MIT License
43.49k stars 2.27k forks source link

Invalid Version: undefined #5943

Closed LeoMsky closed 3 years ago

LeoMsky commented 3 years ago

Everything is OK yesterday，but I've had this problem since I installed it again this morning image

krnlde commented 3 years ago

Yes most of the projects I work on are using monorepos (mostly via yarn workspaces).

@devongovett Thank you for this! I changed the structure of our boilerplate project with a pseudo monorepo (yarn workspaces + git modules) and it worked perfectly! We've just pulled the trigger, we've moved to parcel 2!

Sorry, for being a bit unrelated here: @fedegratti are you able to trigger a recompile when changing code in another workspace than the current one? In multiple projects I worked in the Watcher doesn't pick them up, in v1 it does.

fedegratti commented 3 years ago

@fedegratti are you able to trigger a recompile when changing code in another workspace than the current one? In multiple projects I worked in the Watcher doesn't pick them up, in v1 it does.

Yes, but one thing I noticed is that the recompile is not triggered for all files. I think it only works for files that are imported somewhere in the executable code. I'm not completely sure about this yet, but this is how I feel it works after doing some tests.

dkadrios commented 3 years ago

Like others here, I've periodically tried to upgrade and have run into troubles every time. This last attempt a couple of weeks back got me the furthest yet. Everything was working, including lazy loading React components which hadn't worked for me in past attempts. The only problem I ran into this time was that the generated source maps weren't usable within Chrome. While that's a showstopper for me, it gives me hope that v2 is getting way more stable.

Velodata commented 2 years ago

Came across this problem myself today while trying to run a two year old tutorial regarding React.js and Wordpress.

After much poking and prodding I discovered that it helps to clear your npm cache files. It seems that once you download the wrong version of @babel (at least in the context of the problem defined in this thread) then that is the version which keeps getting loaded into your node-modules directory.

AjiteshMDK commented 2 years ago

Getting the same error. can anyone please help me on fixing it? already have followed all the solution mentioned here, still no luck. any help on this would be great.

image

Git repo - https://github.com/AjiteshMDK/GeoLocation-Update/issues/1

SerzhLe commented 2 years ago

FYI reverting to 1.12.3 seems to work

Yes! Try to downgrade to this version. I used v.1.12.4. I have spent half a day finding a solution - and only this switching worked for me!