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
NodeJS > 12 supports natively import.meta.url but setting it as a target generates an empty meta.url.
Warning is "import.meta" is not available in the configured target environment and will be empty
"import.meta" is not available in the configured target environment and will be empty
Forcefully setting the target to "es2020" causes instead other 2020 syntax to fail in node 12, 13, 14 like, for example, null coalescing operators.
Solution: esbuild with target node>12 should use the native import.meta.url
The text was updated successfully, but these errors were encountered:
Thanks for the report. I think this is just due to a typo in esbuild's compatibility table:
esbuild/scripts/compat-table.js
Line 154 in 150a018
This should be true, not false. Will fix.
true
false
Sorry, something went wrong.
ef61169
Successfully merging a pull request may close this issue.
NodeJS > 12 supports natively import.meta.url but setting it as a target generates an empty meta.url.
Warning is
"import.meta" is not available in the configured target environment and will be empty
Forcefully setting the target to "es2020" causes instead other 2020 syntax to fail in node 12, 13, 14 like, for example, null coalescing operators.
Solution: esbuild with target node>12 should use the native import.meta.url
The text was updated successfully, but these errors were encountered: