We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given both TypeScript and ClosureCompiler have fixed es2018 targeting, good to lock down es2018 instead of esnext?
es2018
esnext
The text was updated successfully, but these errors were encountered:
yeah!
Sorry, something went wrong.
No branches or pull requests
Given both TypeScript and ClosureCompiler have fixed
es2018
targeting, good to lock downes2018
instead ofesnext
?The text was updated successfully, but these errors were encountered: