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

IE11 compatibility problem #119

Open
tomczhang opened this issue Oct 12, 2020 · 1 comment
Open

IE11 compatibility problem #119

tomczhang opened this issue Oct 12, 2020 · 1 comment

Comments

@tomczhang
Copy link

As usual, typechecker will be used as a dependecies. And typechecker doesn't transfer the index.ts to es5, such as line 254 has the keyword "const".

If webpack has a setting which has "exclude: /node_modules/", the output js won't work well in IE11.

@balupton
Copy link
Member

which ecmascript version would you want to target for web browsers? boundation is setup for typescript projects to target the ecmascript version of the previous year - which should be suitable for evergreen browsers - if you can propose an alternative for this complexity, and why you are targetting non-evergreen browsers - then something can be considered

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

2 participants