v1.15.7

Compare Source

Bug Fixes

• (es/minifier) Prevent unsafe sequence merging in super() calls (#​11381) (eb02780)

• (es/transformer) Fix variable declaration for nullish coalescing in else-if branches (#​11384) (6746002)

• (es/transforms) Update _ts_rewrite_relative_import_extension helper code (#​11382) (1ec444e)

Features

• (es/transformer) Merge private_properties_in_object (#​11378) (769c9d2)

Performance

• (es/minifier) Optimize data structures of ProgramData (#​11374) (3639523)

Refactor

• (es/transformer) Port var injector (#​11383) (cfff553)

v1.15.6

Compare Source

v1.15.5

Compare Source

Bug Fixes

• (es/parser) Fix bump length (#​11372) (ec5c1bc)

• (es/transforms) Adjust import rewriter pass before inject helpers pass (#​11371) (8516991)

v1.15.4

Compare Source

Bug Fixes

• (es/compat) Preserve return value for single-property object destructuring (#​11334) (847ad22)

• (es/compat) Fix generator transform for compound assignments, for-in, and labeled break (#​11339) (9b6bedd)

• (es/compat) Destructuring evaluation order (#​11337) (49d04c7)

• (es/compat) Fix parameter default value evaluation order with object rest (#​11352) (2ebb261)

• (es/fixer) Preserve parens around IFFE in binary expressions within sequences (#​11324) (a4c84ea)

• (es/helpers) Avoid extra trap calls on excluded keys in object rest spread (#​11338) (4662caf)

• (es/minifier) Fix debug cargo feature (#​11325) (be86fad)

• (es/minifier) Fix optimization pass for merge_imports (#​11331) (ca2f7ed)

• (es/parser) Don't call bump_bytes in the continue_if of byte_search! (#​11328) (583619d)

• (es/parser) Support type-only string literal in import specifiers (#​11333) (07762f1)

• (es/parser) Handle TypeScript expressions in destructuring patterns (#​11353) (160ec34)

• (es/transformer) Complete replace_this_in_expr implementation (#​11361) (58c4067)

• (es/transformer) Fix pass order (#​11370) (373048a)

Features

• (es/minifier) Optimize typeof x == "undefined" to typeof x > "u" (#​11367) (a5e144b)

• (es/parser) Support no_paren parser option (#​11359) (5b9d77c)

• (es/parser) Revert no_paren parser option (#​11362) (57a8731)

• (es/transfomer) Add modules to prepare porting (#​11347) (68d740c)

• (es/transform) Add common fields (#​11346) (1a8759f)

• (es/transformer) Merge async-to-generator (#​11355) (c388e87)

• (es/transformer) Merge async_to_generator (#​11358) (25f3a47)

• (es/transformer) Merge object_rest_spread (#​11357) (752188e)

• (es/transformer) Merge nullish_coalescing (#​11365) (5fb686a)

• (es/transformer) Merge logical_assignment_operators (#​11369) (94946fa)

Performance

• (es/compat) Merge exponentation_operator (#​11310) (0ef3637)

• (es/compat) Merge optional_catch_binding (#​11313) (468d20c)

• (es/compat) Use merged transformer (#​11366) (c4a5e79)

• (es/parser) Optimize byte_search! (#​11323) (67f67c1)

• (es/parser) Small optimization after byte-based lexer (#​11340) (c92ea4e)

• (es/parser) Use slice rather than matching keywords (#​11341) (b6ad2cb)

• (parser) Make all parsers work by byte instead of char (#​11318) (725efd1)

v0.27.2

Compare Source

• Allow import path specifiers starting with #/ (#​4361)

  Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

  This change was contributed by @​hybrist.

• Automatically add the -webkit-mask prefix (#​4357, #​4358)

  This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

  /* Original code */
  main {
    mask: url(x.png) center/5rem no-repeat
  }
  
  /* Old output (with --target=chrome110) */
  main {
    mask: url(x.png) center/5rem no-repeat;
  }
  
  /* New output (with --target=chrome110) */
  main {
    -webkit-mask: url(x.png) center/5rem no-repeat;
    mask: url(x.png) center/5rem no-repeat;
  }

  This change was contributed by @​BPJEnnova.

• Additional minification of switch statements (#​4176, #​4359)

  This release contains additional minification patterns for reducing switch statements. Here is an example:

  // Original code
  switch (x) {
    case 0:
      foo()
      break
    case 1:
    default:
      bar()
  }
  
  // Old output (with --minify)
  switch(x){case 0:foo();break;case 1:default:bar()}
  
  // New output (with --minify)
  x===0?foo():bar();

• Forbid using declarations inside switch clauses (#​4323)

  This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced using declarations. These were previously allowed inside case and default clauses in switch statements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.

  Here is an example of code that is no longer allowed:

  switch (mode) {
    case 'read':
      using readLock = db.read()
      return readAll(readLock)
  
    case 'write':
      using writeLock = db.write()
      return writeAll(writeLock)
  }

  That code will now have to be modified to look like this instead (note the additional { and } block statements around each case body):

  switch (mode) {
    case 'read': {
      using readLock = db.read()
      return readAll(readLock)
    }
    case 'write': {
      using writeLock = db.write()
      return writeAll(writeLock)
    }
  }

  This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).

v10.26.0

Compare Source