8000 JSX Optional Chaining results in Unexpected Token error on compilation · Issue #58 · failwyn/WebCompiler · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

JSX Optional Chaining results in Unexpected Token error on compilation #58

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.

Sign up for GitHub

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

Jump to bottom
Open
jbaldwinson opened this issue Nov 29, 2022 · 2 comments
Open

JSX Optional Chaining results in Unexpected Token error on compilation #58

jbaldwinson opened this issue Nov 29, 2022 · 2 comments

Comments

@jbaldwinson
Copy link

Installed product versions

  • Visual Studio: 17.4.1
  • This extension: 1.14.8

Description

Added a null check chaining operator into a JSX file, and can no longer compile into JS. I think this is due to the version of Babel being targeted.

Steps to recreate

  1. Have a JSX file
  2. Add a null chaining operator
  3. try to compile the jsx file
  4. Get the error
@failwyn
Copy link
Owner
failwyn commented Nov 29, 2022

I can take another look into upgrading Babel, but last time I tried, it caused other issues and I ended up having to revert back to the old version.

#15

@jbaldwinson
Copy link
Author

Yeah, I saw that commit and rollback. Happy to help in anyway I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@failwyn @jbaldwinson
0