chore(deps): update all non-major dependencies #48
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:
20.3.1
->20.8.6
0.19.0
->0.19.4
8.46.0
->8.51.0
5.0.0
->5.0.1
15.10.0
->15.11.0
8.9.1
->8.9.2
3.0.1
->3.0.3
Release Notes
evanw/esbuild (esbuild)
v0.19.4
Compare Source
Fix printing of JavaScript decorators in tricky cases (#3396)
This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:
Allow pre-release versions to be passed to
target
(#3388)People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's
target
setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed totarget
and do something reasonable with them.v0.19.3
Compare Source
Fix
list-style-type
with thelocal-css
loader (#3325)The
local-css
loader incorrectly treated all identifiers provided tolist-style-type
as a custom local identifier. That included identifiers such asnone
which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:Note that this bug only affected code using the
local-css
loader. It did not affect code using thecss
loader.Avoid inserting temporary variables before
use strict
(#3322)This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before
use strict
directives:Adjust TypeScript
enum
output to better approximatetsc
(#3329)TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:
However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:
The template literal initializer for
PRESENT
is treated as a string while the template literal initializer forMISSING
is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior oftsc
but in the case where the behavior divergestsc
reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see thedeclare
keyword), which esbuild deliberately doesn't do.Ignore case in CSS in more places (#3316)
This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:
Please never actually write code like this.
Improve the error message for
null
entries inexports
(#3377)Package authors can disable package export paths with the
exports
map inpackage.json
. With this release, esbuild now has a clearer error message that points to thenull
token inpackage.json
itself instead of to the surrounding context. Here is an example of the new error message:Parse and print the
with
keyword inimport
statementsJavaScript was going to have a feature called "import assertions" that adds an
assert
keyword toimport
statements. It looked like this:The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.
Instead, the current proposal is to add a feature called "import attributes" instead that adds a
with
keyword to import statements. It looks like this:This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new
with
keyword. Thewith
keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.v0.19.2
Compare Source
Update how CSS nesting is parsed again
CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:
Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.
Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.
Fix a scope-related bug with
--drop-labels=
(#3311)The recently-released
--drop-labels=
feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.Make renamed CSS names unique across entry points (#3295)
Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.
Fix CSS ordering bug with
@layer
before@import
CSS lets you put
@layer
rules before@import
rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the@import
rules and then joining files together in the right order. But with@layer
, CSS files may now need to be split apart into multiple pieces in the bundle. For example:Unwrap nested duplicate
@media
rules (#3226)With this release, esbuild's CSS minifier will now automatically unwrap duplicate nested
@media
rules:These rules are unlikely to be authored manually but may result from using frameworks such as Tailwind to generate CSS.
v0.19.1
Compare Source
Fix a regression with
baseURL
intsconfig.json
(#3307)The previous release moved
tsconfig.json
path resolution before--packages=external
checks to allow thepaths
field intsconfig.json
to avoid a package being marked as external. However, that reordering accidentally broke the behavior of thebaseURL
field fromtsconfig.json
. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.Parse TypeScript type arguments for JavaScript decorators (#3308)
When parsing JavaScript decorators in TypeScript (i.e. with
experimentalDecorators
disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:Fix glob patterns matching extra stuff at the end (#3306)
Previously glob patterns such as
./*.js
would incorrectly behave like./*.js*
during path matching (also matching.js.map
files, for example). This was never intentional behavior, and has now been fixed.Change the permissions of esbuild's generated output files (#3285)
This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's
fs.writeFileSync
function. Since most tools written in JavaScript usefs.writeFileSync
, this should make esbuild more consistent with how other JavaScript build tools behave.The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for
fs.writeFileSync
defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.Fix a subtle CSS ordering issue with
@import
and@layer
With this release, esbuild may now introduce additional
@layer
rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:This CSS should set the body background to
green
, which is what happens in the browser. Previously esbuild generated the following output which incorrectly sets the body background tored
:This difference in behavior is because the browser evaluates
a.css
+b.css
+a.css
(in CSS, each@import
is replaced with a copy of the imported file) while esbuild was only writing outb.css
+a.css
. The first copy ofa.css
wasn't being written out by esbuild for two reasons: 1) bundlers care about code size and try to avoid emitting duplicate CSS and 2) when there are multiple copies of a CSS file, normally only the last copy matters since the last declaration with equal specificity wins in CSS.However,
@layer
was recently added to CSS and for@layer
the first copy matters because layers are ordered using their first location in source code order. This introduction of@layer
means esbuild needs to change its bundling algorithm. An easy solution would be for esbuild to write outa.css
twice, but that would be inefficient. So what I'm going to try to have esbuild do with this release is to write out an abbreviated form of the first copy of a CSS file that only includes the@layer
information, and then still only write out the full CSS file once for the last copy. So esbuild's output for this edge case now looks like this:The behavior of the bundled CSS now matches the behavior of the unbundled CSS. You may be wondering why esbuild doesn't just write out
a.css
first followed byb.css
. That would work in this case but it doesn't work in general because for any rules outside of a@layer
rule, the last copy should still win instead of the first copy.Fix a bug with esbuild's TypeScript type definitions (#3299)
This release fixes a copy/paste error with the TypeScript type definitions for esbuild's JS API:
This fix was contributed by @privatenumber.
eslint/eslint (eslint)
v8.51.0
Compare Source
Features
0a9c433
feat: Add--no-warn-ignored
CLI option for flat config (#17569) (Domantas Petrauskas)977e67e
feat: logical-assignment-operators to report expressions with 3 operands (#17600) (Yosuke Ota)Bug Fixes
f976b2f
fix: make rule severity case-sensitive in flat config (#17619) (Milos Djermanovic)0edfe36
fix: Ensure crash error messages are not duplicated (#17584) (Nicholas C. Zakas)dd79abc
fix:eslint-disable
to be able to parse quoted rule names (#17612) (Yosuke Ota)d2f6801
fix: Ensure correct code path for && followed by ?? (#17618) (Nicholas C. Zakas)Documentation
ee5be81
docs: default tosourceType: "module"
in rule examples (#17615) (Francesco Trotta)1aa26df
docs: Add more examples for multiline-ternary (#17610) (George Ashiotis)47d0b44
docs: Update README (GitHub Actions Bot)dbf831e
docs: use generated og image (#17601) (Percy Ma)1866da5
docs: Update README (GitHub Actions Bot)Chores
1ef39ea
chore: upgrade @eslint/js@8.51.0 (#17624) (Milos Djermanovic)f8c7403
chore: package.json update for @eslint/js release (ESLint Jenkins)2665552
test: fix flat config linter tests to use Linter in flat config mode (#17616) (Milos Djermanovic)7b77bcc
chore: Refactor CodePathState (#17510) (Nicholas C. Zakas)bc77c9a
chore: Document and refactor ForkContext (#17566) (Nicholas C. Zakas)24e1f14
chore: Refactor and document CodePath (#17558) (Nicholas C. Zakas)v8.50.0
Compare Source
Features
27d5a9e
feat: add suggestions to array-callback-return (#17590) (Tanuj Kanti)f9082ff
feat: flat-rule-tester make sure default config always matches (#17585) (fnx)83914ad
feat: Implement SourceCode#applyInlineConfig() (#17351) (Nicholas C. Zakas)22a5582
feat: add ruleno-object-constructor
, deprecateno-new-object
(#17576) (Francesco Trotta)85a3d9e
feat: allowVoid option in array-callback-return (#17564) (Tanuj Kanti)Bug Fixes
cc4d26b
fix: Ensure deprecated context.parserServices warns (#17593) (Nicholas C. Zakas)1ea4cfb
fix: Ensure all RuleTester tests all deprecated context methods (#17587) (Nicholas C. Zakas)aa1b657
fix: wrong suggestion and message inno-misleading-character-class
(#17571) (Yosuke Ota)Documentation
1800537
docs: Fix and standardize JSX code examples (#17591) (Francesco Trotta)48a44a7
docs: Add correct/incorrect tags toprefer-arrow-callback
(#17589) (Francesco Trotta)20893d4
docs: fix incorrect tag's place (#17575) (Tanuj Kanti)bd7a71f
docs: Update README (GitHub Actions Bot)Chores
f8a8a2d
chore: upgrade @eslint/js@8.50.0 (#17599) (Milos Djermanovic)38ada6d
chore: package.json update for @eslint/js release (ESLint Jenkins)v8.49.0
Compare Source
Features
da09f4e
feat: Implement onUnreachableCodePathStart/End (#17511) (Nicholas C. Zakas)32b2327
feat: Emit deprecation warnings in RuleTester (#17527) (Nicholas C. Zakas)acb7df3
feat: add newenforce
option tolines-between-class-members
(#17462) (Nitin Kumar)Documentation
ecfb54f
docs: Update README (GitHub Actions Bot)de86b3b
docs: updateno-promise-executor-return
examples (#17529) (Nitin Kumar)032c4b1
docs: add typescript template (#17500) (James)cd7da5c
docs: Update README (GitHub Actions Bot)Chores
b7621c3
chore: remove browser test fromnpm test
(#17550) (Milos Djermanovic)cac45d0
chore: upgrade @eslint/js@8.49.0 (#17549) (Milos Djermanovic)cd39508
chore: package.json update for @eslint/js release (ESLint Jenkins)203a971
ci: bump actions/checkout from 3 to 4 (#17530) (dependabot[bot])a40fa50
chore: use eslint-plugin-jsdoc's flat config (#17516) (Milos Djermanovic)926a286
test: replace Karma with Webdriver.IO (#17126) (Christian Bromann)f591d2c
chore: Upgrade config-array (#17512) (Nicholas C. Zakas)v8.48.0
Compare Source
Features
1fbb3b0
feat: correct update direction infor-direction
(#17483) (Francesco Trotta)d73fbf2
feat: rule tester do not create empty valid or invalid test suites (#17475) (fnx)ee2f718
feat: Allowvoid
in ruleno-promise-executor-return
(#17282) (nopeless)Bug Fixes
7234f6a
fix: update RuleTester JSDoc and deprecations (#17496) (Jonas Berlin)Documentation
7a51d77
docs: no-param-reassign mention strict mode (#17494) (Stephen Hardy)9cd7ac2
docs: addfetch
script to package.json conventions (#17459) (Nitin Kumar)cab21e6
docs: advice for inline disabling of rules (#17458) (Ashish Yadav)056499d
docs: fix example of flat config from plugin (#17482) (Francesco Trotta)9e9edf9
docs: update documentation URL in error message (#17465) (Nitin Kumar)Chores
8dd3cec
chore: upgrade @eslint/js@8.48.0 (#17501) (Milos Djermanovic)6d0496e
chore: package.json update for @eslint/js release (ESLint Jenkins)9d4216d
chore: Refactor and document CodePathSegment (#17474) (Nicholas C. Zakas)v8.47.0
Compare Source
Features
53d7508
feat: update regex for methods withthisArg
(#17439) (Francesco Trotta)Bug Fixes
631648e
fix: do not report on shadowed constructors inno-new-wrappers
(#17447) (Francesco Trotta)Documentation
a766a48
docs: document lack of config file names (#17442) (James)a1635d6
docs: Update README (GitHub Actions Bot)47a0859
docs: updaterequire-unicode-regexp.md
as following up #17402 (#17441) (SUZUKI Sosuke)fcdc85d
docs: Update README (GitHub Actions Bot)2a92b6c
docs: update with "Specifying Parser Options" (#17435) (Cheol-Won)d743ed3
docs: add metadata for parser/processor (#17438) (Huáng Jùnliàng)224376c
docs: Update README (GitHub Actions Bot)a41a8e4
docs: update script names in README (#17432) (Nitin Kumar)Chores
bf69aa6
chore: Update dependencies (#17456) (Nicholas C. Zakas)0e45760
chore: package.json update for @eslint/js release (ESLint Jenkins)757bfe1
chore: Remove add-to-triage (#17450) (Nicholas C. Zakas)b066640
chore: standardize npm script names (#17431) (Nitin Kumar)6b2410f
chore: Update add-to-triage.yml (#17444) (Nicholas C. Zakas)prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.0.1
Compare Source
Patch Changes
21a7146
Thanks @krist7599555! - fix:parserPath
type might beundefined
on Eslint Falt Confignetlify/cli (netlify-cli)
v15.11.0
Compare Source
Features
pnpm/pnpm (pnpm)
v8.9.2
Compare Source
Patch Changes
preinstall
lifecycle script is present #7206.Our Gold Sponsors
Our Silver Sponsors
prettier/prettier (prettier)
v3.0.3
Compare Source
diff
Add
preferUnplugged: true
topackage.json
(#15169 by @fisker and @so1ve)Prettier v3 uses dynamic imports, user will need to unplug Prettier when Yarn's PnP mode is enabled, add
preferUnplugged: true
topackage.json
, so Yarn will install Prettier as unplug by default.Support shared config that forbids
require()
(#15233 by @fisker)If an external shared config package is used, and the package
exports
don't haverequire
ordefault
export.In Prettier 3.0.2 Prettier fails when attempt to
require()
the package, and throws an error.Allow argument of
require()
to break (#15256 by @fisker)Do not print trailing commas in arrow function type parameter lists in
ts
code blocks (#15286 by @sosukesuzuki)Support TypeScript 5.2
using
/await using
declaration (#15321 by @sosukesuzuki)Support for the upcoming Explicit Resource Management feature in ECMAScript.
using
/await using
declarationv3.0.2
Compare Source
diff
Break after
=
of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#15204 by @seiyab)Do not add trailing comma for grouped scss comments (#15217 by @auvred)
Print
declare
andexport
keywords for nested namespace (#15249 by @sosukesuzuki)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.