-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught SyntaxError: Unexpected token ')'
in watch mode
#7916
Comments
Possibly fixed by #7886, which hasn't been released yet. You could try the latest nightly version and see if that fixes it? |
To try to fix parcel-bundler/parcel#7916. Also remove pointless --dist-dir and npx from build scripts.
I can still reproduce this on 2.0.0-nightly.1039+211502e55. |
Original code (from https://unpkg.com/netlify-cms@2.10.190/dist/cms.js): function oe() {
var e, t, n, r = 35 * G + 0,
o = Z[r];
if (o) return G = o.nextPos, o.result;
for (e = G, t = [], n = ae(); n !== i;) t.push(n), n = ae();
return t !== i && (e, t = t), e = t, Z[r] = {
nextPos: G,
result: e
}, e
} Probably due to: parcel/packages/transformers/js/core/src/lib.rs Lines 344 to 348 in 211502e
Should the |
As far as I understand it, Also, this is caused by the |
🐛 bug report
When I try to build a module depending on
netlify-cms
usingparcel
, I get the following error:It seems to work when building using
parcel build
.🎛 Configuration (.babelrc, package.json, cli command)
Building with
npx parcel admin/index.html --dist-dir public/admin/ --public-url .
No special configuration, see the minimal example.
🤔 Expected Behavior
The code should be produced without error.
😯 Current Behavior
Viewing the generated file in Firefox or Chromium reveals a syntax error.
🔦 Context
The line points to the following code:
For some reason neither Chromium nor Firefox seems to use the source maps for this so I cannot determine the original source code.
💻 Code Sample
https://github.com/jtojnar/repro/tree/738c2d442b504378b145edde2fdc52c8b2e217a0/parcel-netlify-cms
🌍 Your Environment
The text was updated successfully, but these errors were encountered: