chore: upgrade Parcel

[louisgv]

Details

An initial attempt at upgrading Parcel. Tracking the following blockers:

• @parcel/resolver-default: Could not find extended tsconfig parcel-bundler/parcel#9057 <- might need to do the patch or swap out the js packager, re: [BUG] Sass import error in Parcel 2.9.3 #786

I need help with:

• The new parcel rust stuff seems to foobar'ed a lot of path resolution: Invalid path of @parcel\config-default\index.json parcel-bundler/parcel#9319
• Fixing up the js packager (either rewrite it, patch it, or ping the Parcel devs to fix it)
• There's a huge issue with the upstream resolver that's been around since 2.9.3, and doesn't seem to be fixed in 2.10.2. Need someone to triage and chase it down with the Parcel folks.
• Upgrade our HMR pipeline, incorporating some idea from: https://github.com/parcel-bundler/parcel/pull/9068/files (Specifically, with how it handles non-code import. Basically they transformed it into a bundle of the file itself, and a CS to hot reload. Didn't know you can send out 2 bundles at once?!)
• Test the updated framework out locally

If you're down to help, feel free to ping me on Discord or in the comment section.

Code of Conduct

• I agree to follow this project's Code of Conduct
• I agree to license this contribution under the MIT LICENSE
• I checked the current PR for duplication.

Contacts

• (OPTIONAL) Discord ID:

If your PR is accepted, we will award you with the Contributor role on Discord server.

To join the server, visit: https://www.plasmo.com/s/d

[louisgv]

Getting this error, coming from parcel/core: https://github.com/parcel-bundler/parcel/blob/d58e3361ad16c90bb44a2cad8edae31df66c7578/packages/core/core/src/requests/ParcelConfigRequest.js#L209C31-L245

🔴 ERROR  | Failed to parse .parcelrc

[seawatts]

Any progress here? It's blocking #1076

[tbrockman]

@seawatts I've started to work on this and have a branch which works for the most part, but it can't really be merged into main as is. Unfortunately there are some issues in the latest versions parcel (all the way up to the latest release, 2.12.0), one which leads to intermittent build failures (fixed in @nightly thankfully) and another which may cause runtime failures due to scope-hoisting removing necessary references (waiting response here parcel-bundler/parcel#9972).

Might be possible to cut a beta release for it though, but that'd be up to @louisgv.

[pippinmole]

Hi @tbrockman, is it worth picking this back up?

[BalutaAlex]

Hi, it looks like upgrading Parcel to a newer version would resolve many issues, as there has been significant development upstream. Can we come up with a plan for this? Some things to check in order to make this work, or maybe some historic context on how to upgrade it/or how things have been done.

cc @louisgv

[encodedz]

Hey, this PR looks like very much needed, as said it can potentially resolve alot of issue relating to parcel imports system.

@louisgv Do you think this one can be pushed?

[louisgv]

@pippinmole @tbrockman thought? There are a couple of moving parts with the parcel core that I think would be nice to use upstream directly if it works :-?

[pippinmole]

@pippinmole @tbrockman thought? There are a couple of moving parts with the parcel core that I think would be nice to use upstream directly if it works :-?

Is it possible to upgrade mix and match parcel package (@parcel/*) versions or do we have to keep them all the same? Thinking of an iterative approach to the upgrade since there are a lot of issues upstream

[tbrockman]

Hey hey! I stopped working on this but https://github.com/tbrockman/plasmo/tree/parcel is available for reference (updates parcel dependencies, switches to using pnpm catalog: in the workspace to make it easier to bump shared dependencies across all workspace projects, removes some of the plasmo plugins which are presumably no longer necessary, and probably some other changes I can't remember).

Doesn't look like anything has changed as far as the blocker I ran into on my branch though. When using recursive pnpm commands (i.e, building examples here) module resolution would fail (though would pass when executing a single build):

with-tabs:build: @parcel/core: Failed to resolve '@plasmo-static-common/react' from 
with-tabs:build: './with-tabs/.plasmo/tabs/delta-flyer.tsx'
with-tabs:build:   /home/tbrockman/workspace/dev/plasmo/examples/with-tabs/.plasmo/tabs/delta-flyer.tsx:4:27
with-tabs:build:     3 | 
with-tabs:build:   > 4 | import { getLayout } from "@plasmo-static-common/react"
with-tabs:build:   >   |                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
with-tabs:build:     5 | 
with-tabs:build:     6 | // @ts-ignore
with-tabs:build: @parcel/resolver-default: Cannot find module '@plasmo-static-common/react'

At this point I think I lost motivation and just opted to start using esbuild for my projects instead.