41 Replies
Thanks for the report- do you have any log before that error block? Also can I see a verbose version of the log? (use
pnpm dev --verbose))
I'm investigated the issue and it's likely due to the parcel upgrade, so I'm triage with upstream atm
it's related to this: https://github.com/parcel-bundler/parcel/issues/6892Gave +1 Rep to @holden
Also I recall you're using css modules, what other feature of plasmo are you using? Just wanted to triage and pinpoint the issue
I just released a canary version with the bundler upgraded to align with parcel's. If you got a chance please try it out and lmk if the error's gone!
(to use canary, simply swap out the version in package.json with
canary)
parcel bundler related LOC: https://github.com/parcel-bundler/parcel/blob/v2/packages/packagers/js/src/ScopeHoistingPackager.js#L784
@holden let's continue here
We've seen this issue before, it's related to the asset bundle size I think... how big is your dev bundle?
Also can you share the log for pnpm build --verbose
Just released another canary, can you try again plasmo@0.59.2-alpha.2
@holden
Do you use any package that might polyfill system nodejs package?
for example do you do anything that might import os, buffer, punycode etc?Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
@holden has reached level 3. GG!
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
this is very helpful - narrowed it down to the transformer
I will get another canary patch up sometime tmr
there's a bug with 0.59.x regarding the release tag oh boy....
Can you try out
plasmo@0.59.2-alpha.3 when you got a chanceUnknown User•2y ago
Message Not Public
Sign In & Join Server To View
@holden can you take a look at the tree of
.plasmo/gen-assets as well as the chrome-mv3.plasmo.manifest.json file inside .plasmo
Would be very helpful to see the content of these
The latest canary fixed a problem with how plasmo build was using the wrong env when bundling for prod, which I thought would explain why you're getting the assset skipped/not found error. However, that doesn't seem to be the case :d....Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
hmmm.. ok interesting - your manifest file does not have the
default_popup
So after it load the default_icon, the framework then look into compiling the default popup, to which it couldn't find the entry in your manifest I think
^ disregard the above. A couple of the example I have also doesn't have the default_popup and it worked just fine
@holden when ur up, can you update to 0.59.2-alpha.4 and run plasmo build --verbose again <= I can't reproduce with any of the existing example so I just added more logging location, hoping to narrow it down furtherUnknown User•2y ago
Message Not Public
Sign In & Join Server To View
Alright so we're clear it's in the packaer territory
@holden can you show me the content of your
tabs directory
I think the issue that I nailed down is related to the web accessible resource reconciling
Also does it work if you remove tabs from the wars list? And why was tabs needed to be inside the wars list (for iframe?)?
Just updated canary with .5 which has some logic that check for entry file copying into wars
pls try it out and lmk if it fixed the issue. If not Imma place more verbose log and we will further narrow down this issueUnknown User•2y ago
Message Not Public
Sign In & Join Server To View
interesting....
the only other place where this error could occur would be in the bunder, but it didn't throw at the bundler but at the packager :d.....