v7.0.5

Compare Source

Bug Fixes

• deps: update all non-major dependencies (#​20406) (1a1cc8a)
• remove special handling for Accept: text/html (#​20376) (c9614b9)
• watch assets referenced by new URL(, import.meta.url) (#​20382) (6bc8bf6)

Miscellaneous Chores

• deps: update dependency rolldown to ^1.0.0-beta.27 (#​20405) (1165667)

Code Refactoring

• use foo.endsWith("bar") instead of /bar$/.test(foo) (#​20413) (862e192)

v0.17.0

Compare Source

Minor Changes

• 3f736b6: feat(runtime): add createInstance api and deprecate init

Patch Changes

• 3f736b6: chore(runtime): add RUNTIME-009 error code
• 3f736b6: refactor(runtime): rename FederationRuntimePlugin to ModuleFederationRuntimePlugin
• 3f736b6: chore: rename FederationHost to ModuleFederation
• Updated dependencies [3f736b6]
  • @​module-federation/runtime-core@​0.17.0
  • @​module-federation/sdk@​0.17.0
  • @​module-federation/error-codes@​0.17.0

v1.4.5

Compare Source

What's Changed

• fix(wasm32-wasip1-threads): process never exit if trap in threads (#​156)

Full Changelog: toyobayashi/emnapi@v1.4.4...v1.4.5

v0.25.8

Compare Source

• Fix another TypeScript parsing edge case (#​4248)

  This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

  class CachedDict {
    #has = (a: string) => dict.has(a);
    has = window
      ? (word: string): boolean => this.#has(word)
      : this.#has;
  }

• Fix a regression with the parsing of source phase imports

  The change in the previous release to parse source phase imports failed to properly handle the following cases:

  import source from 'bar'
  import source from from 'bar'
  import source type foo from 'bar'

  Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

Compare Source

• Parse and print JavaScript imports with an explicit phase (#​4238)

  This release adds basic syntax support for the defer and source import phases in JavaScript:

  • defer

    This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

    import defer * as foo from "<specifier>";
    const bar = await import.defer("<specifier>");

    Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

  • source

    This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

    import source foo from "<specifier>";
    const bar = await import.source("<specifier>");

    Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".

  This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

• Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

  This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

  Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

• Fix a TypeScript parsing edge case (#​4241)

  This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

  x = a ? (b) : c => d;
  y = a ? (b) : c => d : e;

  The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

• Inline small constant strings when minifying

  Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

  // Original code
  const foo = 'foo'
  console.log({ [foo]: true })
  
  // Old output (with --minify --bundle --format=esm)
  var o="foo";console.log({[o]:!0});
  
  // New output (with --minify --bundle --format=esm)
  console.log({foo:!0});

  Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

v5.62.0

Compare Source

• Support .ts extension in toLilconfigutility for default TS configs (#​1157) (cbfb9c3) - thanks @​what1s1ove!
• Update reporters to have the correct name for the default reporter (#​1165) (bf81146) - thanks @​gavinhenderson!
• Add audit as a valid command for bun (#​1168) (014cbaa) - thanks @​carlosedp!
• Fix Angular plugin to allow for @​angular/build (#​1175) (0754130) - thanks @​davidlj95!
• Correctly detect used/unused namespace exports that begin with double underscores (#​1180) (259a2f6) - thanks @​akallem!
• Rename tsconfig-loader.ts → load-tsconfig.ts (61280b0)
• Support absolute path for config argument (b606681)
• Fix formatting (ebc9202)
• Add bun.lock support in @​knip/create-config (#​1182) (da80ab3) - thanks @​ShooTeX!
• Support new biome config extends definition (#​1177) (07439ef) - thanks @​Thomascogez!
• Support Vitest projects configuration for dynamic project discovery (#​1171) (cd0ed32) - thanks @​yyxi!
• Fix up ESLint flat config resolution (replace #​1173) (021ecff)
• Reuse existing entry/production patterns in astro plugin (e65f709)
• Edit docs (10f8a4f)

v1.7.0

Compare Source

🚀 Features

• a4dae73 linter: Introduce LintPlugins to store builtin + custom plugins (#​12117) (camc314)

v2.26.1

Compare Source

Bug Fixes

• forEachObj,keys,mapKeys,mapValues,omitBy,pickBy: support branded keys (#​1151) (96e20e2), closes #​752

v2.26.0

Compare Source

Features

• stringToPath: improve compatibility with Lodash (#​1150) (0fde627), closes #​779

v4.45.1

Compare Source

2025-07-15

Bug Fixes

• Resolve crash when using certain conditional expressions (#​6009)

Pull Requests

• #​6009: Add hasDeoptimizedCache flag for ConditionalExpression (@​TrickyPi)

v1.7.1

Compare Source

   🐞 Bug Fixes

• Fix the problem with the VitePress warning "node:path" has been externalized for browser compatibility  -  by @​okineadev (55515)
• Fix version in package.json  -  by @​okineadev (1986b)
• llms.txt: Search index.md also in VitePress rewrites  -  by @​okineadev (dfcd8)

    View changes on GitHub