Skip to content
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

Module parse failed: Unexpected token patronum.umd.js #255

Open
psdarko opened this issue Oct 27, 2022 · 3 comments
Open

Module parse failed: Unexpected token patronum.umd.js #255

psdarko opened this issue Oct 27, 2022 · 3 comments
Labels
question Further information is requested

Comments

@psdarko
Copy link

psdarko commented Oct 27, 2022

Optional chaining ?. on many places of code

p({ type: t, name: o, scopeName: n?.name, value: e });

[email protected]

@sergeysova sergeysova added the bug Something isn't working label Nov 9, 2022
@AlexandrHoroshih
Copy link
Member

Hello!

Could you add a bit more details? Which browsers you target, how your project is built?

@sergeysova
Copy link
Member

I recommend to transpile your node_modules for target browsers.

Because optional chaining is enabled for two years already:

image

@sergeysova sergeysova added question Further information is requested and removed bug Something isn't working labels Nov 9, 2022
@KlonD90
Copy link

KlonD90 commented Dec 26, 2022

@sergeysova please compile by yoursefl it's or provide another entrypoint will be nice for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants