PiTiLeZarD
commented
2 years ago So after a bit of digging, it seems like the issue comes from the fact that my index.html is loading the index.js with type="module" and that tells it that import.meta is a thing but once loaded in chrome it's not happy with Uncaught SyntaxError: Cannot use 'import.meta' outside a module. If I remove this though, I get a @parcel/transformer-js: Browser scripts cannot have imports or exports.. Catch 22
Not quite sure why it worked before, I reverted to parcel 2.1.1 which was the last version that used to package my stuff but it seems like I have the issue there as well. But it might be due to the fact that I have:
"@parcel/core@^2.1.1":
version "2.3.1"
resolved "https://registry.yarnpkg.com/@parcel/core/-/core-2.3.1.tgz#d4f0092552b46f33ea21e45c78c5cd5c1399a214"
integrity sha512-Fzj8OxICQ0dKqu+haq1LP/yxmE1ryALIddZrgmn4JSoNiZVtPJMOxidozyl+3bnEq0mRyH5i38CDFRUWl9dqKQ==in my yarn.lock regardless of whatever I tell it to install.
When I'm on the latest version I have tons of other issues packaging my app with libraries that don't seem to match in my yarn workspaces anymore. At this point, the "no config easy parcel" is giving me quite a bit of grief Β―_(γ)_/Β―
github-actions[bot]
π bug report
A recent update created this issue. It used to work.
I'm importing a font this way:
The dev build works fine, production build leads to:
the console.log is the line that introduces the issue but in context it's used differently, I just narrowed it down to "as soon as I use the font, the compiler has to include it and compiles to something that uses import.meta, and that breaks in the browser"
π Configuration (.babelrc, package.json, cli command)
I can't share my package.json, it's quite a few in a yarn workspaces but just for the big lines, apollo, mui, the font is used in a theme but commenting all that out leaves the issue as is.
my .parcelrc looks like this:
scripts:
π€ Expected Behavior
What used to happen, I don't know what that was, but it didn't compile to a import.meta and it worked fine for a long while.
π¦ Context
The issue happens only on the production build, the dev build works fine.
A custom font in a mui theme.
π Your Environment
Thanks very much for reading this and even more if you have the answer to this. I've checked open issues, and couldn't find anything relevant, if you do, I'm happy if you point me towards it.
Cheers