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

Issues in IE11 with untranspiled export #98

Closed
Scoutski opened this issue May 20, 2019 · 2 comments
Closed

Issues in IE11 with untranspiled export #98

Scoutski opened this issue May 20, 2019 · 2 comments

Comments

@Scoutski
Copy link

Scoutski commented May 20, 2019

Hi, I just wanted to ask whether or not it would be possible to fully transpile the acorn-jsx export to IE friendly ES5 as it contains a class declaraction (line 72) return class extends Parser { that when included in an IE11 project, causes IE11 to fail? If you're happy for me to, I can create a PR to do this?

If you want, I can provide more info. Regardless, I appreciate your time and work, thanks.

@RReverser
Copy link
Member

Yes, it should be possible, just configure your transpiler to include Acorn-JSX.

@dmt0
Copy link

dmt0 commented Mar 6, 2020

I'm using webpack-babel-env-deps to determine which packages to transpile to ES5. acorn-jsx escapes it (and had to be added manually), since there's no engines field in package.json. Would be great if things would "just work". 🙂

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

No branches or pull requests

3 participants