futurebad.blogg.se

Permit top-level await in dead code branches ( #​2853)Īdding top-level await to a file has a few consequences with esbuild: With this release, esbuild's serve mode will also respond to HTTP HEAD requests, which are just like HTTP GET requests except that the body of the response is omitted. Previously esbuild's serve mode only responded to HTTP GET requests. Implement HTTP HEAD requests in serve mode ( #​2851) This will no longer be allowed starting with this release.

Previously esbuild incorrectly allowed the definite assignment assertion operator with class methods. For example, you might think that the following CSS is equivalent to a. In particular, there is still some debate about changing the fundamental way that CSS nesting works. While the syntax has been decided, the semantics are still in flux. However, I'm not implementing lowering of nested CSS to non-nested CSS for older browsers yet. So you can now use esbuild to bundle CSS containing nested rules and try them out in a browser that supports CSS nesting (which includes nightly builds of both Chrome and Safari). This release updates esbuild's pass-through handling of CSS nesting syntax to match the latest specification changes. The prefix that was previously required in some cases is now gone, and nested rules no longer have to start with & (as long as they don't start with an identifier or function token). The syntax for the upcoming CSS nesting feature has recently changed. Update esbuild's handling of CSS nesting to match the latest specification changes ( #​1945) template-literal: node v4+ => node v10+ (an increase)Įach of these adjustments was identified by comparing against data from the node-compat-table package and was manually verified using old node executables downloaded from.optional-chain: node v16.9+ => node v16.1+ (a decrease).