Any plans to migrate Parcel to V2?

[aboveyunhai]

Current Behavior

The weird part is that inside the devDependencies, parcel is ^1.12.3,
but when I run npm i and npm outdated, parcel is always installed as 1.12.4 due to some dep dependency requirement.

The current project will always fail in /example project due to the Parcel bug.
It's been discussed for a while but it seems like this forks does not address this critical issue.

So I had to do hard roll back to 1,12.3 by npm i parcel@1.12.3, which creates some questionable warnings.

Though it's just a example playground that has nothing to do with the true package, the developer experience is quite unpleasing.

Expected behavior

Run npm run start without problems

Suggested solution(s)

Additional context

Your environment

windows

[aladdin-add]

yes, but i slightly prefer vite.js; anyway, parcel v1 should have been went away.
// cc @sidwebworks

[aboveyunhai]

yes, but i slightly prefer vite.js; anyway, parcel v1 should have been went away. // cc @sidwebworks

Good to know it's in progress, as long as the tool works as intent and better, I'm fine with any tools.

[aladdin-add]

should have been fixed in v0.19.1. :🎉

[aboveyunhai]

should have been fixed in v0.19.1. :🎉

Apologize for the naïve question, is it possible to update existing package via cli?
My current package is still using parcel (technically 0.17.1), I did not find any useful doc to update without recreating a new project.

[aladdin-add]

No straightforward way to get it. you can just create a new one, and copy the example/ to your existing package. 😄

[aboveyunhai]

No straightforward way to get it. you can just create a new one, and copy the example/ to your existing package. 😄

No worry, I did understand the problem behinds it, just want to get the confirmation so I don't miss anything besides doc. Thx for your work!