Comments (1)
"Yet" is there both because at the time the issue regarding ES5 support hadn't been closed yet, and because it's something that esbuild might hypothetically still support in the future. However, I have since closed the issue about ES5 support because I have decided to not prioritize esbuild lowering things to ES5 given how widespread ES6 support is. So it's not that esbuild can't do it or that it won't, but that it's very low priority.
FWIW the reason destructuring isn't supported by your target build environment is that it includes edge16
. Wikipedia has this to say about Microsoft's non-Chromium "Edge Legacy" browser (see here):
Microsoft stopped supporting Microsoft Edge Legacy on March 9, 2021.[64][65] On April 13, 2021, Microsoft released a cumulative monthly security update which replaced Edge Legacy with the new Chromium-based Edge.[66]
So it sounds like Microsoft is both a) not supporting this browser at all anymore, meaning it's now insecure and unsafe to use on the Internet due to lack of security updates and b) already pushed out code to actively overwrite it with their Chromium-based browser over two years ago. So one option to consider is dropping support for these really old+insecure+deprecated versions of Microsoft Edge (i.e. changing edge16
to edge18
to pick up destructuring support).
from esbuild.
Related Issues (20)
- `esnext` target doesn't transform using declarations but `es2022` does HOT 2
- Default exports not handled correctly when external=true and module is dynamically imported (node16)
- Is there a problem here? does this make sense? HOT 4
- Glob-style imports with partial directory name substitutions
- Option to assign default export to globalName for iife format HOT 3
- Running esbuild under npm explore no longer works HOT 1
- esbuild not work well with package.json has "exports:{"./*": "./*"}" HOT 2
- re-create package.json with only externalized dependencies
- SyntaxError: The requested module X does not provide an export named Y since code modification HOT 1
- Cross-Platform Development Problem HOT 6
- CSS media query range syntax not downleveled
- Object rest and function scope HOT 4
- DCE doesn't remove unreferenced `new Regexp`. HOT 1
- CVE-2023-45288 HOT 3
- Throwing an error within a plugin does not stop the build
- Metafile not output to the `outdir` HOT 2
- Output is incorrect when there is an import declaration with an import clause that has one type only import specifier HOT 3
- invalid code generation HOT 3
- Building on top of esbuild Analyze HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from esbuild.