chore(deps): update all non-major dependencies #37
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:
^18.15.11
->^18.16.3
^0.17.15
->^0.17.18
^8.38.0
->^8.39.0
^1.17.0
->^1.20.0
8.2.0
->8.3.1
^2.8.7
->^2.8.8
^3.20.2
->^3.21.2
^4.2.1
->^4.3.3
^0.30.0
->^0.30.1
^5.78.0
->^5.81.0
Release Notes
evanw/esbuild
v0.17.18
Compare Source
Fix non-default JSON import error with
export {} from
(#3070)This release fixes a bug where esbuild incorrectly identified statements of the form
export { default as x } from "y" assert { type: "json" }
as a non-default import. The bug did not affect code of the formimport { default as x } from ...
(only code that used theexport
keyword).Fix a crash with an invalid subpath import (#3067)
Previously esbuild could crash when attempting to generate a friendly error message for an invalid subpath import (i.e. an import starting with
#
). This happened because esbuild originally only supported theexports
field and the code for that error message was not updated when esbuild later added support for theimports
field. This crash has been fixed.v0.17.17
Compare Source
Fix CSS nesting transform for top-level
&
(#3052)Previously esbuild could crash with a stack overflow when lowering CSS nesting rules with a top-level
&
, such as in the code below. This happened because esbuild's CSS nesting transform didn't handle top-level&
, causing esbuild to inline the top-level selector into itself. This release handles top-level&
by replacing it with the:scope
pseudo-class:Support
exports
inpackage.json
forextends
intsconfig.json
(#3058)TypeScript 5.0 added the ability to use
extends
intsconfig.json
to reference a path in a package whosepackage.json
file contains anexports
map that points to the correct location. This doesn't automatically work in esbuild becausetsconfig.json
affects esbuild's path resolution, so esbuild's normal path resolution logic doesn't apply.This release adds support for doing this by adding some additional code that attempts to resolve the
extends
path using theexports
field. The behavior should be similar enough to esbuild's main path resolution logic to work as expected.Note that esbuild always treats this
extends
import as arequire()
import since that's what TypeScript appears to do. Specifically therequire
condition will be active and theimport
condition will be inactive.Fix watch mode with
NODE_PATH
(#3062)Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the
NODE_PATH
environment variable. While esbuild supports this too, previously a bug prevented esbuild's watch mode from picking up changes to imported files that were contained directly in aNODE_PATH
directory. You're supposed to useNODE_PATH
for packages, but some people abuse this feature by putting files in that directory instead (e.g.node_modules/some-file.js
instead ofnode_modules/some-pkg/some-file.js
). The watch mode bug happens when you do this because esbuild first tries to readsome-file.js
as a directory and then as a file. Watch mode was incorrectly waiting forsome-file.js
to become a valid directory. This release fixes this edge case bug by changing watch mode to watchsome-file.js
as a file when this happens.v0.17.16
Compare Source
Fix CSS nesting transform for triple-nested rules that start with a combinator (#3046)
This release fixes a bug with esbuild where triple-nested CSS rules that start with a combinator were not transformed correctly for older browsers. Here's an example of such a case before and after this bug fix:
Support
--inject
with a file loaded using thecopy
loader (#3041)This release now allows you to use
--inject
with a file that is loaded using thecopy
loader. Thecopy
loader copies the imported file to the output directory verbatim and rewrites the path in theimport
statement to point to the copied output file. When used with--inject
, this means the injected file will be copied to the output directory as-is and a bareimport
statement for that file will be inserted in any non-copy output files that esbuild generates.Note that since esbuild doesn't parse the contents of copied files, esbuild will not expose any of the export names as usable imports when you do this (in the way that esbuild's
--inject
feature is typically used). However, any side-effects that the injected file has will still occur.eslint/eslint
v8.39.0
Compare Source
Features
3f7af9f
feat: ImplementSourceCode#markVariableAsUsed()
(#17086) (Nicholas C. Zakas)Documentation
6987dc5
docs: Fix formatting in Custom Rules docs (#17097) (Milos Djermanovic)4ee92e5
docs: Update README (GitHub Actions Bot)d8e9887
docs: Custom Rules cleanup/expansion (#16906) (Ben Perlmutter)1fea279
docs: Clarify how to add to tsc agenda (#17084) (Nicholas C. Zakas)970ef1c
docs: Update triage board location (Nicholas C. Zakas)6d8bffd
docs: Update README (GitHub Actions Bot)Chores
60a6f26
chore: upgrade @eslint/js@8.39.0 (#17102) (Milos Djermanovic)d5ba5c0
chore: package.json update for @eslint/js release (ESLint Jenkins)f57eff2
ci: run tests on Node.js v20 (#17093) (Nitin Kumar)9d1b8fc
perf: Binary search in token storeutils.search
(#17066) (Francesco Trotta)07a4435
chore: Add request for minimal repro to bug report (#17081) (Nicholas C. Zakas)eac4943
refactor: remove unnecessary use ofSourceCode#getAncestors
in rules (#17075) (Milos Djermanovic)0a7b60a
chore: update description ofSourceCode#getDeclaredVariables
(#17072) (Milos Djermanovic)6e2df71
chore: remove unnecessary references to the LICENSE file (#17071) (Milos Djermanovic)Shinigami92/eslint-define-config
v1.20.0
Compare Source
diff
v1.19.0
Compare Source
diff
v1.18.0
Compare Source
diff
parserOptions.project
to betrue
(#185)pnpm/pnpm
v8.3.1
Compare Source
Patch Changes
node-fetch
to fix an error that happens on Node.js 20 #6424.Our Gold Sponsors
Our Silver Sponsors
v8.3.0
Compare Source
Minor Changes
pnpm pack
command using thepack-gzip-level
setting #6393.--check
flag topnpm dedupe
. No changes will be made tonode_modules
or the lockfile. Exits with a non-zero status code if changes are possible.pnpm install --resolution-only
re-runs resolution to print out any peer dependency issues #6411.Patch Changes
publishConfig.directory
of an injected workspace dependency does not exist #6396.Our Gold Sponsors
Our Silver Sponsors
prettier/prettier
v2.8.8
Compare Source
This version is a republished version of v2.8.7.
A bad version was accidentally published and it can't be unpublished, apologies for the churn.
rollup/rollup
v3.21.2
Compare Source
2023-04-30
Bug Fixes
Pull Requests
v3.21.1
Compare Source
2023-04-29
Bug Fixes
arguments
variable (#4965)Pull Requests
v3.21.0
Compare Source
2023-04-23
Features
Pull Requests
v3.20.7
Compare Source
2023-04-21
Bug Fixes
Pull Requests
v3.20.6
Compare Source
2023-04-18
Bug Fixes
Pull Requests
v3.20.5
Compare Source
2023-04-18
Bug Fixes
Pull Requests
v3.20.4
Compare Source
2023-04-17
Bug Fixes
Pull Requests
v3.20.3
Compare Source
2023-04-16
Bug Fixes
shouldTransformCachedModule
(#4932)Pull Requests
vitejs/vite
v4.3.3
Compare Source
v4.3.2
Compare Source
v4.3.1
Compare Source
v4.3.0
Compare Source
Vite 4.3 is out! Read the announcement blog post here
In this minor, we focused on improving the dev server performance. The resolve logic got streamlined, improving hot paths and implementing smarter caching for finding
package.json
, TS config files, and resolved URL in general.You can read a detailed walkthrough of the performance work done in this blog post by one of Vite Contributors: How we made Vite 4.3 faaaaster 🚀.
This sprint resulted in speed improvements across the board compared to Vite 4.2.
These are the performance improvements as measured by sapphi-red/performance-compare, which tests an app with 1000 React Components cold and warm dev server startup time as well as HMR times for a root and a leaf component:
You can read more information about the benchmark here
Features
isFileServingAllowed
as public utility (#12894) (93e095c), closes #12894data:
uris (#12645) (4886d9f), closes #12645Performance
depsCacheDirPrefix
value forisOptimizedDepFile
(#12601) (edbd262), closes #12601safeRealpath
ingetRealpath
(#12551) (cec2320), closes #12551Bug Fixes
Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.