Sourced from typescript's releases.

TypeScript 4.8.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 4.8.0 (Beta).
• fixed issues query for Typescript 4.8.1 (RC).
• fixed issues query for Typescript 4.8.2 (Stable).
• fixed issues query for Typescript 4.8.3 (Stable).
• fixed issues query for Typescript 4.8.4 (Stable).

Downloads are available on:

• npm
• Visual Studio 2022/2019 (Select new version in project options)
• NuGet package

• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from ava's releases.

v4.0.1

What's Changed

• Fix encoding of large snapshot data by @​novemberborn in avajs/ava#2936

Full Changelog: https://github.com/avajs/ava/compare/v4.0.0...v4.0.1

AVA 4

We're celebrating the new year with the official AVA 4 release! 🎊

npm install -D ava

The cool new stuff 🆒

Worker threads 🧑‍💼

By default, test files are now run in worker threads! Huge thanks to @​dnlup for landing this.

Test files should run a little quicker, since it's easier to spin up a worker thread than a child process. You can use --no-worker-threads on the command line, or workerThreads: false in your AVA configuration, to fall back to using child processes.

Shared workers are no longer experimental 🎊

Shared workers are no longer experimental. This is a powerful feature that loads a program in a worker thread in AVA's main process and then communicate with code running in the test workers. This enables your tests to better utilize shared resources during a test run, as well as providing opportunities to set up these resources before tests start (or clean them up after).

When you use watch mode, shared workers remain loaded across runs.

Improved test selection 🤳

AVA selects test files based on your package.json or ava.config.* configuration files. When used on the CLI you can then provide patterns to select a subset of these files.

You can now pass a folder and AVA will select the test files contained therein. Or you can provide a specific JavaScript file and AVA will run it even if it wasn’t selected by your configuration.

If AVA finds files based on the configuration, but none of those were selected to the CLI arguments, it now prints a warning.

Better monorepo support 🚝

AVA now looks for ava.config.* files in parent directories, until it finds a directory with a .git directory (or file). This lets you specify AVA configuration at the top of your monorepo and still run AVA from within each package.

New snapshot format 📸

@​ninevra has worked tirelessly on landing a new snapshot format. It contains all information necessary to regenerate the report file. This allows for snapshots to be updated even if tests or assertions are skipped.

Previously failing test files run first 🏃

AVA now records which test files failed in the previous run. It then prioritizes testing these files when you run AVA again. Thanks @​bunysae!

ESM support 🤾

... (truncated)

• 6b63b1b 4.0.1
• c384e9a Fix encoding of large snapshot data
• 9bc615e 4.0.0
• f09742f Clean up documentation in preparation for AVA 4
• 0187779 Dependency updates
• 29024af Test compatibility with TypeScript 4.5
• 8df118b Use AVA 4 for the self-hosted tests
• bedd1d0 Remove dependency on equal-length
• d4ec097 Improve wording in TypeScript recipe
• b3a1b72 Mention experimental specifier resolution in TypeScript recipe
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.16.13

• Publish a new bundle visualization tool

  While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

  • https://esbuild.github.io/analyze/

  You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

  • Which packages are included in my bundle?
  • How did a specific file get included?
  • How small did a specific file compress to?
  • Was a specific file tree-shaken or not?

  I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

• Fix --metafile and --mangle-cache with --watch (#1357)

  The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

• Add an original field to the metafile

  The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

v0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

  • JS:

    esbuild.build({
      bundle: true,
      loader: { '': 'css' },
    })
    

  • Go:

    api.Build(api.BuildOptions{
      Bundle: true,
      Loader: map[string]api.Loader{"": api.LoaderCSS},
    

... (truncated)

Sourced from esbuild's changelog.

0.16.13

• Publish a new bundle visualization tool

  While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

  • https://esbuild.github.io/analyze/

  You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

  • Which packages are included in my bundle?
  • How did a specific file get included?
  • How small did a specific file compress to?
  • Was a specific file tree-shaken or not?

  I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

• Fix --metafile and --mangle-cache with --watch (#1357)

  The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

• Add an original field to the metafile

  The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

  • JS:

    esbuild.build({
      bundle: true,
      loader: { '': 'css' },
    })
    

  • Go:

    api.Build(api.BuildOptions{
    

... (truncated)

• 0db0b46 publish 0.16.13 to npm
• eda632d mention the bundle analyzer in the release notes
• 9234378 add the original field to the metafile
• d59ca10 feat: add markdown to guessed mime types (#2784)
• 59fd941 add a custom error message for #2783
• 6837c35 enable source maps for the json loader
• 16e77e7 fix test flake in watchMetafile
• 78a9be4 always use a plugin for post-build actions
• e4f32bb watch mode: print metafile analysis after rebuilds
• 867ef14 test coverage for: Cannot use "watch" with "serve"
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

  • JS:

    esbuild.build({
      bundle: true,
      loader: { '': 'css' },
    })
    

  • Go:

    api.Build(api.BuildOptions{
      Bundle: true,
      Loader: map[string]api.Loader{"": api.LoaderCSS},
    })
    

  In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

v0.16.11

• Avoid a syntax error in the presence of direct eval (#2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }
  console.log(!!foo)
  // Transformed code
  if (true) {
  let foo2 = function() {
  };
  

... (truncated)

Sourced from esbuild's changelog.

0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

  • JS:

    esbuild.build({
      bundle: true,
      loader: { '': 'css' },
    })
    

  • Go:

    api.Build(api.BuildOptions{
      Bundle: true,
      Loader: map[string]api.Loader{"": api.LoaderCSS},
    })
    

  In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

0.16.11

• Avoid a syntax error in the presence of direct eval (#2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }
  console.log(!!foo)
  // Transformed code
  if (true) {
  

... (truncated)

• ddda86e publish 0.16.12 to npm
• ffe1c5b limit type in package.json to .js and friends
• 466473b fix #2776: assume extensionless files are js
• f42ca4a allow loaders for extensionless files
• 1755592 publish 0.16.11 to npm
• ba6246a fix #2773: eval dependency symlinks instead of reading symlink target (#2774)
• cf8ea74 Fix typo in js_parser_lower.go (#2771)
• 0a60afe additional test coverage
• 46347f7 fix #2761: avoid syntax error with direct eval
• c94ad6c explicit pre-release version error (#2766, #2760)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​typescript-eslint/eslint-plugin's releases.

v5.47.1

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

v5.47.0

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

v5.46.1

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/typescript-eslint

v5.46.0

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

v5.45.1

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#6118) (5d49d5d)
• parser: remove the jsx option requirement for automatic jsx pragma resolution (#6134) (e777f5e)

v5.45.0

5.45.0 (2022-11-28)

... (truncated)

Sourced from @​typescript-eslint/eslint-plugin's changelog.

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#6118) (5d49d5d)

5.45.0 (2022-11-28)

Bug Fixes

• eslint-plugin: [array-type] --fix flag removes parentheses from type (#5997) (42b33af)
• eslint-plugin: [keyword-spacing] prevent crash on no options (#6073) (1f19998)
• eslint-plugin: [member-ordering] support private fields (#5859) (f02761a)
• eslint-plugin: [prefer-readonly] report if a member's property is reassigned (#6043) (6e079eb)

Features

• eslint-plugin: [member-ordering] add a required option for required vs. optional member ordering (#5965) (2abadc6)

5.44.0 (2022-11-21)

... (truncated)

• 6ffce79 chore: publish v5.47.1
• 0f3f645 fix(ast-spec): correct some incorrect ast types (#6257)
• ccd45d4 fix(eslint-plugin): [member-ordering] correctly invert optionalityOrder (#6256)
• a2c08ba chore: publish v5.47.0
• 9e35ef9 feat(eslint-plugin): [no-floating-promises] add suggestion fixer to add an 'a...
• 6b3ed1d docs: fixed typo "foo.property" (#6180)
• c943b84 chore: publish v5.46.1
• 47241bb docs: overhaul branding and add new logo (#6147)
• 1e1573a chore: publish v5.46.0
• d91a5fc fix(eslint-plugin): [ban-types] update message to suggest object instead of...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.16.11

• Avoid a syntax error in the presence of direct eval (#2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }
  console.log(!!foo)
  // Transformed code
  if (true) {
  let foo2 = function() {
  };
  var foo = foo2;
  console.log(!!foo2);
  foo2 = null;
  console.log(!!foo2);
  }
  console.log(!!foo);
  

  In the above example, the original code should print true false true because it's not run in strict mode (it doesn't contain "use strict" and is not an ES module). The code that esbuild generates has been transformed such that it prints true false true regardless of whether it's run in strict mode or not.

  However, this transformation is impossible if the code contains direct eval because direct eval "poisons" all containing scopes by preventing anything in those scopes from being renamed. That prevents esbuild from splitting up accesses to foo into two separate variables with different names. Previously esbuild still did this transformation but with two variables both named foo, which is a syntax error. With this release esbuild will now skip doing this transformation when direct eval is present to avoid generating code with a syntax error. This means that the generated code may no longer behave as intended since the behavior depends on the run-time strict mode setting instead of the strict mode setting present in the original source code. To fix this problem, you will need to remove the use of direct eval.

• Fix a bundling scenario involving multiple symlinks (#2773, #2774)

  This release contains a fix for a bundling scenario involving an import path where multiple path segments are symlinks. Previously esbuild was unable to resolve certain import paths in this scenario, but these import paths should now work starting with this release. This fix was contributed by @​onebytegone.

v0.16.10

• Change the default "legal comment" behavior again (#2745)

  The legal comments feature automatically gathers comments containing @license or @preserve and puts the comments somewhere (either in the generated code or in a separate file). This behavior used to be on by default but was disabled by default in version 0.16.0 because automatically inserting comments is potentially confusing and misleading. These comments can appear to be assigning the copyright of your code to another entity. And this behavior can be especially problematic if it happens automatically by default since you may not even be aware of it happening. For example, if you bundle the TypeScript compiler the preserving legal comments means your source code would contain this comment, which appears to be assigning the copyright of all of your code to Microsoft:

  /*! *****************************************************************************
  Copyright (c) Microsoft Corporation. All rights reserved.
  Licensed under the Apache License, Version 2.0 (the "License"); you may not use
  this file except in compliance with the License. You may obtain a copy of the
  License at http://www.apache.org/licenses/LICENSE-2.0
  THIS CODE IS PROVIDED ON AN AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED
  WARRANTIES OR CONDITIONS OF TITLE, FITNESS FOR A PARTICULAR PURPOSE,
  

... (truncated)

Sourced from esbuild's changelog.

0.16.11

• Avoid a syntax error in the presence of direct eval (#2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }
  console.log(!!foo)
  // Transformed code
  if (true) {
  let foo2 = function() {
  };
  var foo = foo2;
  console.log(!!foo2);
  foo2 = null;
  console.log(!!foo2);
  }
  console.log(!!foo);
  

  In the above example, the original code should print true false true because it's not run in strict mode (it doesn't contain "use strict" and is not an ES module). The code that esbuild generates has been transformed such that it prints true false true regardless of whether it's run in strict mode or not.

  However, this transformation is impossible if the code contains direct eval because direct eval "poisons" all containing scopes by preventing anything in those scopes from being renamed. That prevents esbuild from splitting up accesses to foo into two separate variables with different names. Previously esbuild still did this transformation but with two variables both named foo, which is a syntax error. With this release esbuild will now skip doing this transformation when direct eval is present to avoid generating code with a syntax error. This means that the generated code may no longer behave as intended since the behavior depends on the run-time strict mode setting instead of the strict mode setting present in the original source code. To fix this problem, you will need to remove the use of direct eval.

• Fix a bundling scenario involving multiple symlinks (#2773, #2774)

  This release contains a fix for a bundling scenario involving an import path where multiple path segments are symlinks. Previously esbuild was unable to resolve certain import paths in this scenario, but these import paths should now work starting with this release. This fix was contributed by @​onebytegone.

0.16.10

• Change the default "legal comment" behavior again (#2745)

  The legal comments feature automatically gathers comments containing @license or @preserve and puts the comments somewhere (either in the generated code or in a separate file). This behavior used to be on by default but was disabled by default in version 0.16.0 because automatically inserting comments is potentially confusing and misleading. These comments can appear to be assigning the copyright of your code to another entity. And this behavior can be especially problematic if it happens automatically by default since you may not even be aware of it happening. For example, if you bundle the TypeScript compiler the preserving legal comments means your source code would contain this comment, which appears to be assigning the copyright of all of your code to Microsoft:

  /*! *****************************************************************************
  Copyright (c) Microsoft Corporation. All rights reserved.
  Licensed under the Apache License, Version 2.0 (the "License"); you may not use
  this file except in compliance with the License. You may obtain a copy of the
  License at http://www.apache.org/licenses/LICENSE-2.0
  THIS CODE IS PROVIDED ON AN AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  

... (truncated)

• 1755592 publish 0.16.11 to npm
• ba6246a fix #2773: eval dependency symlinks instead of reading symlink target (#2774)
• cf8ea74 Fix typo in js_parser_lower.go (#2771)
• 0a60afe additional test coverage
• 46347f7 fix #2761: avoid syntax error with direct eval
• c94ad6c explicit pre-release version error (#2766, #2760)
• 0fea6ae publish 0.16.10 to npm
• 270a210 fix #2715: allow package subpaths with alias
• 1ec8085 fix #2390: transform w/ external legal comments
• 6a73c5e fix #2757: duplicate function definition edge case
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​typescript-eslint/parser's releases.

v5.47.1

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

v5.47.0

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

v5.46.1

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/typescript-eslint

v5.46.0

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

v5.45.1

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#6118) (5d49d5d)
• parser: remove the jsx option requirement for automatic jsx pragma resolution (#6134) (e777f5e)

v5.45.0

5.45.0 (2022-11-28)

... (truncated)

Sourced from @​typescript-eslint/parser's changelog.

5.47.1 (2022-12-26)

Note: Version bump only for package @​typescript-eslint/parser

5.47.0 (2022-12-19)

Note: Version bump only for package @​typescript-eslint/parser

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/parser

5.46.0 (2022-12-08)

Note: Version bump only for package @​typescript-eslint/parser

5.45.1 (2022-12-05)

Bug Fixes

• parser: remove the jsx option requirement for automatic jsx pragma resolution (#6134) (e777f5e)

5.45.0 (2022-11-28)

Note: Version bump only for package @​typescript-eslint/parser

5.44.0 (2022-11-21)

Note: Version bump only for package @​typescript-eslint/parser

5.43.0 (2022-11-14)

Note: Version bump only for package @​typescript-eslint/parser

5.42.1 (2022-11-07)

Note: Version bump only for package @​typescript-eslint/parser

5.42.0 (2022-10-31)

Features

• scope-manager: ignore ECMA version (#5881) (3b8d449)

Reverts

• Revert "feat(scope-manager): ignore ECMA version" (#5888) (2ee81df), closes #5888 #5881

5.41.0 (2022-10-24)

... (truncated)

• 6ffce79 chore: publish v5.47.1
• a2c08ba chore: publish v5.47.0
• c943b84 chore: publish v5.46.1
• 47241bb docs: overhaul branding and add new logo (#6147)
• 1e1573a chore: publish v5.46.0
• 2d0a883 chore: publish v5.45.1
• 46c14cd chore: use short form for nx project names (#6160)
• 0b37822 chore: bump Nx to 15 (#6140)
• e777f5e fix(parser): remove the jsx option requirement for automatic jsx pragma resol...
• 0af822a docs: move remaining docs files into website (#6138)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​napi-rs/cli's releases.

@​napi-rs/cli@​2.14.0

What's Changed

• feat(cli): Darwin universal architecture by @​skirsdeda in napi-rs/napi-rs#1397
• feat(cli): add --zig-link-only option by @​Brooooooklyn in napi-rs/napi-rs#1400

New Contributors

• @​skirsdeda made their first contribution in napi-rs/napi-rs#1397

Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]...@​napi-rs/cli@​2.14.0

@​napi-rs/cli@​2.13.3

2.13.3 (2022-12-15)

Bug Fixes

• cli: set cmake toolchain for android cross build (#1394) (f2c10af)
• cli: template to works with nix (#1391) (36a897e)

@​napi-rs/cli@​2.13.2

2.13.2 (2022-12-09)

Bug Fixes

• cli: ci template upgrade (bd1d3fe)

@​napi-rs/cli@​2.13.1

2.13.1 (2022-12-09)

Bug Fixes

• cli: zig cross armv7 (#1384) (2abc946)

@​napi-rs/cli@​2.13.0

What's Changed

See https://napi.rs/docs/cross-build/summary

• fix(cli): support help command by @​ahaoboy in napi-rs/napi-rs#1355
• feat(cli): auto choose the tooling for cross compiling by @​Brooooooklyn in napi-rs/napi-rs#1367
• chore(cli): upgrade Node.js dependencies by @​Brooooooklyn in napi-rs/napi-rs#1368

Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]...@​napi-rs/cli@​2.13.0

@​napi-rs/cli@​2.13.0-alpha.0

2.13.0-alpha.0 (2022-11-17)

... (truncated)

• 1e8d20a chore: publish
• bc41c97 feat(cli): add --zig-link-only option (#1400)
• 1bcb3a3 Release independent packages
• ef5dffc fix(napi): add back custom gc for Send Buffer (#1399)
• e64f1b6 Merge pull request #1397 from skirsdeda/darwin-universal
• 870552e cli: fix ci-template typo
• cf68288 cli: universal support for CI template
• 4832e93 cli: 'artifacts' command small fix
• fed3584 cli: 'artifacts' command update to deal with universal builds
• cfd8d3d cli: add 'universal' command
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​swc/core's changelog.

[1.3.24] - 2022-12-21

Bug Fixes

• (css/minifier) Don't remove custom variables with different case (#6655) (dd7280d)

• (css/minifier) Fix a bug with a modern hash (#6664) (1d3e06a)

• (es/helpers) Fix loose mode (#6691) (5016ebe)

• (es/minifier) Abort IIFE invoker completely on eval (#6659) (bb9fab8)

• (es/minifier) Don't inline invalid LHS into an update argument (#6680) (7e6ec8d)

• (es/preset-env) Align polyfills with @babel/plugin-polyfill-corejs3 (#6673) (5fed222)

Features

• (css/compat) Support function notation (#6651) (39afc46)

• (css/compat) Support not with multiple arguments (#6668) (352896f)

• (css/compat) Support hwb color (#6687) (b23cf50)

• (css/minifier) Compress alpha in a hex (#6653) (f6292e6)

• (css/minifier) Improve compression of media at-rules (#6665) (2fd3ced)

• (css/parser) Normalize hex colors (#6652) (b257d5d)

• (css/parser) Normalize selector AST (#6657) (649438b)

• (css/parser) Normalize declaration and important (#6663) (1fc97a7)

... (truncated)

• 34ad988 chore: Publish v1.3.24 (#6702)
• af8a3a6 chore: Publish crates
• 025d626 chore(ci): Fix upload of cli binaries (#6701)
• 6124573 chore: Publish crates
• 1c7f003 feat(css/prefixer): Support overflow (#6678)
• 3922ef5 chore: Publish crates
• 2571070 feat(css/parser): Normalize and improve function name (#6667)
• 65c2ab3 chore: Publish crates
• 8a71dbc chore(helpers): Fix license (#6690)
• e49d943 chore: Publish crates
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​typescript-eslint/eslint-plugin's releases.

v5.47.0

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

v5.46.1

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/typescript-eslint

v5.46.0

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

v5.45.1

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#6118) (5d49d5d)
• parser: remove the jsx option requirement for automatic jsx pragma resolution (#6134) (e777f5e)

v5.45.0

5.45.0 (2022-11-28)

Bug Fixes

• eslint-plugin: [array-type] --fix flag removes parentheses from type (#5997) (42b33af)
• eslint-plugin: [keyword-spacing] prevent crash on no options (#6073) (1f19998)
• eslint-plugin: [member-ordering] support private fields (#5859) (f02761a)
• eslint-plugin: [prefer-readonly] report if a member's property is reassigned (#6043) (6e079eb)
• scope-manager: add support for TS4.9 satisfies expression (#6059) (44027db)
• typescript-estree: stub out ts.SatisfiesExpression on old TS versions (#6076) (1302b30)

... (truncated)

Sourced from @​typescript-eslint/eslint-plugin's changelog.

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#6118) (5d49d5d)

5.45.0 (2022-11-28)

Bug Fixes

• eslint-plugin: [array-type] --fix flag removes parentheses from type (#5997) (42b33af)
• eslint-plugin: [keyword-spacing] prevent crash on no options (#6073) (1f19998)
• eslint-plugin: [member-ordering] support private fields (#5859) (f02761a)
• eslint-plugin: [prefer-readonly] report if a member's property is reassigned (#6043) (6e079eb)

Features

• eslint-plugin: [member-ordering] add a required option for required vs. optional member ordering (#5965) (2abadc6)

5.44.0 (2022-11-21)

Bug Fixes

• eslint-plugin: [no-empty-interface] disable autofix for declaration merging with class (#5920) (a4f85b8)
• eslint-plugin: [no-unnecessary-condition] handle index signature type (#5912) (5baad08)
• eslint-plugin: [prefer-optional-chain] handle binary expressions in negated or (#5992) (2778ff0)
• typescript-estree: don't consider a cached program unless it's specified in the current parserOptions.project config (#5999) (530e0e6)

... (truncated)

• a2c08ba chore: publish v5.47.0
• 9e35ef9 feat(eslint-plugin): [no-floating-promises] add suggestion fixer to add an 'a...
• 6b3ed1d docs: fixed typo "foo.property" (#6180)
• c943b84 chore: publish v5.46.1
• 47241bb docs: overhaul branding and add new logo (#6147)
• 1e1573a chore: publish v5.46.0
• d91a5fc fix(eslint-plugin): [ban-types] update message to suggest object instead of...
• 8a91cbd feat(eslint-plugin): [prefer-nullish-coalescing] logic and test for strict nu...
• 2d0a883 chore: publish v5.45.1
• 26c4b46 docs(eslint-plugin): [member-ordering] remove invalid private-abstract-* ment...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​swc/core's changelog.

[1.3.25] - 2023-01-05

Bug Fixes

• (bindings/cli) Skip empty stdin in non tty environments (#6714) (0076418)

• (cli) Use the --source-maps option (#6708) (24cd384)

• (es) Preserve license comments by default (#6703) (58700f2)

• (es) Remove import statement canonicalization (#6716) (b451fa9)

• (es) Fix wasm (#6755) (b46815a)

• (es/compat) Fix syntax context of async-to-generator (#6741) (206c0db)

• (es/minifier) Fix usage counter to fix infinite loop (#6744) (88d40e8)

• (es/parser) Fix priority of >>> (#6748) (65a0d3a)

• (es/plugin) Fix plugin starter template (#6723) (082dc21)

• (es/react) Force refresh if code contains @refresh reset (#6749) (36b26d3)

• (es/utils) Fix detection of hoisting (#6738) (b5d31cc)

• (preset-env) Update data (#6719) (d506c96)

Documentation

• (es) Fix example (#6743) (79afcb5)

Features

... (truncated)

• 7e6e7b1 chore(ci): Fix publish action (#6757)
• ed2277f chore(ci): Fix publish action
• f299101 chore: Publish crates
• 9769a9c chore: Publish v1.3.25 (#6754)
• 1f5c44e chore: Publish crates
• b46815a fix(es): Fix wasm (#6755)
• 3b034d5 chore: Publish crates
• 0076418 fix(bindings/cli): Skip empty stdin in non tty environments (#6714)
• 918a01b chore: Publish crates
• 36b26d3 fix(es/react): Force refresh if code contains @refresh reset (#6749)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.16.14

• Preserve some comments in expressions (#2721)

  Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior:

  import(/* webpackChunkName: "foo" */ '../foo');
  import(/* @vite-ignore */ dynamicVar);
  new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url));
  new Worker(new URL('./path', import.meta.url), /* @vite-ignore */ dynamicOptions);
  

  Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well.

  So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when --minify-syntax is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when --minify-whitespace is enabled (which is automatically enabled when you use --minify).

v0.16.13

• Publish a new bundle visualization tool

  While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

  • https://esbuild.github.io/analyze/

  You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

  • Which packages are included in my bundle?
  • How did a specific file get included?
  • How small did a specific file compress to?
  • Was a specific file tree-shaken or not?

  I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

• Fix --metafile and --mangle-cache with --watch (#1357)

  The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

• Add an original field to the metafile

  The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

v0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

... (truncated)

Sourced from esbuild's changelog.

0.16.14

• Preserve some comments in expressions (#2721)

  Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior:

  import(/* webpackChunkName: "foo" */ '../foo');
  import(/* @vite-ignore */ dynamicVar);
  new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url));
  new Worker(new URL('./path', import.meta.url), /* @vite-ignore */ dynamicOptions);
  

  Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well.

  So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when --minify-syntax is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when --minify-whitespace is enabled (which is automatically enabled when you use --minify).

0.16.13

• Publish a new bundle visualization tool

  While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

  • https://esbuild.github.io/analyze/

  You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

  • Which packages are included in my bundle?
  • How did a specific file get included?
  • How small did a specific file compress to?
  • Was a specific file tree-shaken or not?

  I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

• Fix --metafile and --mangle-cache with --watch (#1357)

  The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

• Add an original field to the metafile

  The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

... (truncated)

• 93328af publish 0.16.14 to npm
• 98bd7c3 preserve comments in import assertions too
• f8311c4 fix #2721: make comment-preservation more general
• c169006 change LegalCommentsBeforeToken into ranges
• 56f4ef9 parser recovery for ?? with || and/or &&
• 85fd2b1 more error text for #2790
• 930f60d link to analyzer in help text
• 0db0b46 publish 0.16.13 to npm
• eda632d mention the bundle analyzer in the release notes
• 9234378 add the original field to the metafile
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​swc-node/register's releases.

@​swc-node/register@​1.5.5

1.5.5 (2023-01-05)

Note: Version bump only for package @​swc-node/register

@​swc-node/register@​1.5.4

1.5.4 (2022-10-06)

Bug Fixes

• register: @​swc/core should be in peerDependencies (cb05cae)

• 83d5f5e chore(release): publish
• e353c1a fix(jest): add externalHelpers:true for jest (#673)
• 639cae5 Pass TypeScript peer dependency to consumer in jest package (#680)
• efd3d01 chore(*): upgrade depes (#682)
• e7bfe70 chore(register): add SWCRC env variable (#678)
• c2b8389 docs: fix sourcemap support installation instructions (#677)
• ef8f5b1 chore(release): publish
• cb05cae fix(register): @​swc/core should be in peerDependencies
• a69aa41 chore(release): publish
• ec9ffeb fix(sourcemap-support): add "tslib" as a dependnecy for "sourcemap-suport" (#...
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​napi-rs/cli's releases.

@​napi-rs/cli@​2.14.1

What's Changed

• [Fix] Quote toml path by @​TheBrenny in napi-rs/napi-rs#1410
• chore(cli): update CI template by @​Brooooooklyn in napi-rs/napi-rs#1416

New Contributors

• @​TheBrenny made their first contribution in napi-rs/napi-rs#1410

Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]...@​napi-rs/cli@​2.14.1

@​napi-rs/cli@​2.14.0

What's Changed

• feat(cli): Darwin universal architecture by @​skirsdeda in napi-rs/napi-rs#1397
• feat(cli): add --zig-link-only option by @​Brooooooklyn in napi-rs/napi-rs#1400

New Contributors

• @​skirsdeda made their first contribution in napi-rs/napi-rs#1397

Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]...@​napi-rs/cli@​2.14.0

@​napi-rs/cli@​2.13.3

2.13.3 (2022-12-15)

Bug Fixes

• cli: set cmake toolchain for android cross build (#1394) (f2c10af)
• cli: template to works with nix (#1391) (36a897e)

@​napi-rs/cli@​2.13.2

2.13.2 (2022-12-09)

Bug Fixes

• cli: ci template upgrade (bd1d3fe)

@​napi-rs/cli@​2.13.1

2.13.1 (2022-12-09)

Bug Fixes

• cli: zig cross armv7 (#1384) (2abc946)

@​napi-rs/cli@​2.13.0

What's Changed

See https://napi.rs/docs/cross-build/summary

... (truncated)

• 83e157e chore: publish
• 895e4ca fix(cli): android cmake build
• abc4566 chore(cli): update CI template (#1416)
• c58972e fix(cli): quote toml path (#1410)
• 76a16be Release independent packages
• 75af3d4 Merge pull request #1414 from napi-rs/delete-reference
• 877d631 fix(napi): only delete reference in custom gc
• d2a492a fix(napi): require higher version of once_cell
• ce4c284 fix(napi): promise leak (#1403)
• a131c8a Merge pull request #1413 from SevInf/feat/future-leak-repro
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​typescript-eslint/parser's releases.

v5.48.0

5.48.0 (2023-01-02)

Bug Fixes

• website: fix typo (#6285) (3f8d105)

Features

• eslint-plugin: specify which method is unbound and added test case (#6281) (cf3ffdd)

v5.47.1

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

v5.47.0

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

v5.46.1

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/typescript-eslint

v5.46.0

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

v5.45.1

5.45.1 (2022-12-05)

... (truncated)

Sourced from @​typescript-eslint/parser's changelog.

5.48.0 (2023-01-02)

Note: Version bump only for package @​typescript-eslint/parser

5.47.1 (2022-12-26)

Note: Version bump only for package @​typescript-eslint/parser

5.47.0 (2022-12-19)

Note: Version bump only for package @​typescript-eslint/parser

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/parser

5.46.0 (2022-12-08)

Note: Version bump only for package @​typescript-eslint/parser

5.45.1 (2022-12-05)

Bug Fixes

• parser: remove the jsx option requirement for automatic jsx pragma resolution (#6134) (e777f5e)

5.45.0 (2022-11-28)

Note: Version bump only for package @​typescript-eslint/parser

5.44.0 (2022-11-21)

Note: Version bump only for package @​typescript-eslint/parser

5.43.0 (2022-11-14)

Note: Version bump only for package @​typescript-eslint/parser

5.42.1 (2022-11-07)

Note: Version bump only for package @​typescript-eslint/parser

5.42.0 (2022-10-31)

Features

• scope-manager: ignore ECMA version (#5881) (3b8d449)

Reverts

... (truncated)

• 4ab9bd7 chore: publish v5.48.0
• 6ffce79 chore: publish v5.47.1
• a2c08ba chore: publish v5.47.0
• c943b84 chore: publish v5.46.1
• 47241bb docs: overhaul branding and add new logo (#6147)
• 1e1573a chore: publish v5.46.0
• 2d0a883 chore: publish v5.45.1
• 46c14cd chore: use short form for nx project names (#6160)
• 0b37822 chore: bump Nx to 15 (#6140)
• e777f5e fix(parser): remove the jsx option requirement for automatic jsx pragma resol...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​typescript-eslint/eslint-plugin's releases.

v5.48.0

5.48.0 (2023-01-02)

Bug Fixes

• website: fix typo (#6285) (3f8d105)

Features

• eslint-plugin: specify which method is unbound and added test case (#6281) (cf3ffdd)

v5.47.1

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

v5.47.0

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

v5.46.1

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/typescript-eslint

v5.46.0

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

v5.45.1

5.45.1 (2022-12-05)

... (truncated)

Sourced from @​typescript-eslint/eslint-plugin's changelog.

5.48.0 (2023-01-02)

Features

• eslint-plugin: specify which method is unbound and added test case (#6281) (cf3ffdd)

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#6256) (ccd45d4)

5.47.0 (2022-12-19)

Features

• eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#5943) (9e35ef9)

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

5.46.0 (2022-12-08)

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#6174) (8a91cbd)

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#6118) (5d49d5d)

5.45.0 (2022-11-28)

Bug Fixes

• eslint-plugin: [array-type] --fix flag removes parentheses from type (#5997) (42b33af)
• eslint-plugin: [keyword-spacing] prevent crash on no options (#6073) (1f19998)
• eslint-plugin: [member-ordering] support private fields (#5859) (f02761a)
• eslint-plugin: [prefer-readonly] report if a member's property is reassigned (#6043) (6e079eb)

... (truncated)

• 4ab9bd7 chore: publish v5.48.0
• cf3ffdd feat(eslint-plugin): specify which method is unbound and added test case (#6281)
• 6ffce79 chore: publish v5.47.1
• 0f3f645 fix(ast-spec): correct some incorrect ast types (#6257)
• ccd45d4 fix(eslint-plugin): [member-ordering] correctly invert optionalityOrder (#6256)
• a2c08ba chore: publish v5.47.0
• 9e35ef9 feat(eslint-plugin): [no-floating-promises] add suggestion fixer to add an 'a...
• 6b3ed1d docs: fixed typo "foo.property" (#6180)
• c943b84 chore: publish v5.46.1
• 47241bb docs: overhaul branding and add new logo (#6147)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)