chore(deps): update all non-major dependencies #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
16.2.1
->16.2.3
5.14.0
->5.15.0
5.14.0
->5.15.0
0.14.25
->0.14.27
3.1.4
->3.1.5
12.3.5
->12.3.7
2.5.1
->2.6.0
^4.15.1
->^4.16.0
Release Notes
conventional-changelog/commitlint
v16.2.3
Compare Source
Note: Version bump only for package @commitlint/cli
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.15.0
Compare Source
Features
parserOptions.emitDecoratorMetadata
(#4646) (e3dd343)typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.15.0
Compare Source
Features
parserOptions.emitDecoratorMetadata
(#4646) (e3dd343)evanw/esbuild
v0.14.27
Compare Source
Avoid generating an enumerable
default
import for CommonJS files in Babel mode (#2097)Importing a CommonJS module into an ES module can be done in two different ways. In node mode the
default
import is always set tomodule.exports
, while in Babel mode thedefault
import passes through tomodule.exports.default
instead. Node mode is triggered when the importing file ends in.mjs
, hastype: "module"
in itspackage.json
file, or the imported module does not have a__esModule
marker.Previously esbuild always created the forwarding
default
import in Babel mode, even ifmodule.exports
had no property calleddefault
. This was problematic because the getter nameddefault
still showed up as a property on the imported namespace object, and could potentially interfere with code that iterated over the properties of the imported namespace object. With this release the getter nameddefault
will now only be added in Babel mode if thedefault
property exists at the time of the import.Fix a circular import edge case regarding ESM-to-CommonJS conversion (#1894, #2059)
This fixes a regression that was introduced in version 0.14.5 of esbuild. Ever since that version, esbuild now creates two separate export objects when you convert an ES module file into a CommonJS module: one for ES modules and one for CommonJS modules. The one for CommonJS modules is written to
module.exports
and exported from the file, and the one for ES modules is internal and can be accessed by bundling code that imports the entry point (for example, the entry point might import itself to be able to inspect its own exports).The reason for these two separate export objects is that CommonJS modules are supposed to see a special export called
__esModule
which indicates that the module used to be an ES module, while ES modules are not supposed to see any automatically-added export named__esModule
. This matters for real-world code both because people sometimes iterate over the properties of ES module export namespace objects and because some people write ES module code containing their own exports named__esModule
that they expect other ES module code to be able to read.However, this change to split exports into two separate objects broke ES module re-exports in the edge case where the imported module is involved in an import cycle. This happened because the CommonJS
module.exports
object was no longer mutated as exports were added. Instead it was being initialized at the end of the generated file after the import statements to other modules (which are converted intorequire()
calls). This release changesmodule.exports
initialization to happen earlier in the file and then double-writes further exports to both the ES module and CommonJS module export objects.This fix was contributed by @indutny.
v0.14.26
Compare Source
Fix a tree shaking regression regarding
var
declarations (#2080, #2085, #2098, #2099)Version 0.14.8 of esbuild enabled removal of duplicate function declarations when minification is enabled (see #610):
This transformation is safe because function declarations are "hoisted" in JavaScript, which means they are all done first before any other code is evaluted. This means the last function declaration will overwrite all previous function declarations with the same name.
However, this introduced an unintentional regression for
var
declarations in which all but the last declaration was dropped if tree-shaking was enabled. This only happens for top-levelvar
declarations that re-declare the same variable multiple times. This regression has now been fixed:This case now has test coverage.
Add support for parsing "instantiation expressions" from TypeScript 4.7 (#2038)
The upcoming version of TypeScript now lets you specify
<...>
type parameters on a JavaScript identifier without using a call expression:With this release, esbuild can now parse these new type annotations. This feature was contributed by @g-plane.
Avoid
new Function
in esbuild's library code (#2081)Some JavaScript environments such as Cloudflare Workers or Deno Deploy don't allow
new Function
because they disallow dynamic JavaScript evaluation. Previously esbuild's WebAssembly-based library used this to construct the WebAssembly worker function. With this release, the code is now inlined without usingnew Function
so it will be able to run even when this restriction is in place.Drop superfluous
__name()
calls (#2062)When the
--keep-names
option is specified, esbuild inserts calls to a__name
helper function to ensure that the.name
property on function and class objects remains consistent even if the function or class name is renamed to avoid a name collision or because name minification is enabled. With this release, esbuild will now try to omit these calls to the__name
helper function when the name of the function or class object was not renamed during the linking process after all:Notice how one of the calls to
__name
is now no longer printed. This change was contributed by @indutny.node-fetch/fetch-blob
v3.1.5
Compare Source
What's Changed
Full Changelog: node-fetch/fetch-blob@v3.1.4...v3.1.5
okonet/lint-staged
v12.3.7
Compare Source
Bug Fixes
--silent
andFORCE_COLOR
settings (d327873)v12.3.6
Compare Source
Bug Fixes
prettier/prettier
v2.6.0
Compare Source
diff
🔗 Release Notes
nodejs/undici
v4.16.0
Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v4.15.1...v4.16.0
Configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.