fix(deps): update all non-major dependencies #322
Merged
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:
^3.0.0
->^3.0.1
^20.10.4
->^20.10.5
^6.14.0
->^6.15.0
^6.14.0
->^6.15.0
^0.19.9
->^0.19.10
^5.0.1
->^5.1.1
^4.6.2
->^4.7.0
^1.0.4
->^1.1.0
Release Notes
sapphiredev/utilities (@sapphire/fetch)
v3.0.1
Compare Source
🐛 Bug Fixes
📝 Documentation
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.15.0
Compare Source
Features
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.15.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
evanw/esbuild (esbuild)
v0.19.10
Compare Source
Fix glob imports in TypeScript files (#3319)
This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.
Fix
require()
glob imports with bundling disabled (#3546)Previously
require()
calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.Fix a panic when transforming optional chaining with
define
(#3551, #3554)This release fixes a case where esbuild could crash with a panic, which was triggered by using
define
to replace an expression containing an optional chain. Here is an example:This fix was contributed by @hi-ogawa.
Work around a bug in node's CommonJS export name detector (#3544)
The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using
import
andexport
syntax and cannot be changed at run time.When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level
exports
object. For example:You can see that node incorrectly thinks the file
confuseNode.js
has an export callednotAnExport
when that file is loaded in an ES module context:To avoid this, esbuild will now rename local variables that use the names
exports
andmodule
when generating CommonJS output for thenode
platform.Fix the return value of esbuild's
super()
shim (#3538)Some people write
constructor
methods that use the return value ofsuper()
instead of usingthis
. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value ofsuper()
intoundefined
. With this release, the return value ofsuper()
will now bethis
instead:Terminate the Go GC when esbuild's
stop()
API is called (#3552)If you use esbuild with WebAssembly and pass the
worker: false
flag toesbuild.initialize()
, then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test callsesbuild.stop()
to clean up esbuild's resources, Deno may complain that asetTimeout()
call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally callingesbuild.stop()
will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker withworker: false
.With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling
clearTimeout()
on these pending timeouts.Apply
/* @​__NO_SIDE_EFFECTS__ */
on tagged template literals (#3511)Tagged template literals that reference functions annotated with a
@__NO_SIDE_EFFECTS__
comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using
@__PURE__
annotations instead of this feature, as they have wider tooling support. The drawback of course is that@__PURE__
annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the@__PURE__
annotation to.Publish builds for IBM AIX PowerPC 64-bit (#3549)
This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with
npm install esbuild
. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.1.1
Compare Source
Patch Changes
b5c0dc5
Thanks @JounQin! - chore: skip formatting inline scripts in pug filesv5.1.0
Compare Source
Minor Changes
#616
3856413
Thanks @BPScott! - Add recommended config for the flat config format.If you are using flat config, import the recommended config from
eslint-plugin-prettier/recommended
. Like the legacy format recommended config, this automatically includes the contents ofeslint-config-prettier
.Patch Changes
#614
5270877
Thanks @BPScott! - Add meta block to plugin. This improves debugging and cachebusting when using the new flat config#603
a63a570
Thanks @filiptammergard! - fix: specifyeslint-config-prettier
as peer dependencyIt's already added to
peerDependenciesMeta
as optional, which means it should also be specified inpeerDependencies
.privatenumber/tsx (tsx)
v4.7.0
Compare Source
Features
This release is also available on:
vitest-dev/vitest (vitest)
v1.1.0
Compare Source
🚀 Features
--workspace
option, fix root resolution in workspaces - by @sheremet-va and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/4773 (67d93)--no-file-parallelism
,--maxWorkers
,--minWorkers
flags - by @sheremet-va and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/4705 (fd5d7)--no-isolate
flag to improve performance, add documentation about performance - by @sheremet-va, @AriPerkkio and Pascal Jufer in https://github.com/vitest-dev/vitest/issues/4777 (4d55a)--exclude
CLI flag - by @Namchee and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4279 (f859e)🐞 Bug Fixes
toHaveProperty
assertion error diff - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/4734 (f8f70)defineWorkspace
fix intellisense and report type errors - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/4743 (9cc36)View changes on GitHub
Configuration
📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 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 Mend Renovate. View repository job log here.