You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fails if I have any custom Babel configurations defined. I'm enabling a few plugins.
I get the following error:
You are using import attributes, without specifying the desired output syntax.
Please specify the "importAttributesKeyword" generator option, whose value can be one of:
- "with" : `import { a } from "b" with { type: "json" };`
- "assert" : `import { a } from "b" assert { type: "json" };`
Server running at http://localhost:1234
🚨 Build failed.
@parcel/transformer-js: Unexpected token `:`. Expected identifier, string literal, numeric literal or [ for the computed key
/mnt/o/...
> 1 | import macro from "./macro.js" with { type: "macro" };
> | ^
I can't seem to figure out how to define the option listed there, I've tried:
Paracel complains a bunch about using redundant Babel stuff:
@parcel/transformer-babel: Parcel includes transpilation by default. Babel config babel.config.json includes the following redundant
presets: @babel/preset-env. Removing these may improve build performance.
The code compiles, but produces nonsensical runtime errors indicating that the bundle is in some way invalid.
I'm using this same config to build my backend code directly with Babel, it it has no issue with the import attributes and doesn't complain about the above config.
The text was updated successfully, but these errors were encountered:
🐛 bug report
Using:
Fails if I have any custom Babel configurations defined. I'm enabling a few plugins.
I get the following error:
I can't seem to figure out how to define the option listed there, I've tried:
Which does nothing, and:
Which produces an error that that isn't a valid option.
If I use the configuration example from the Parcel Macro docs under the Babel section:
Paracel complains a bunch about using redundant Babel stuff:
The code compiles, but produces nonsensical runtime errors indicating that the bundle is in some way invalid.
Am I missing something, or is this a bug?
🎛 Configuration (.babelrc, package.json, cli command)
babel.config.json:
I'm using this same config to build my backend code directly with Babel, it it has no issue with the import attributes and doesn't complain about the above config.
The text was updated successfully, but these errors were encountered: