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.6
->18.15.11
5.56.0
->5.57.0
5.56.0
->5.57.0
0.17.12
->0.17.14
8.36.0
->8.37.0
2.8.6
->2.8.7
1.59.3
->1.60.0
Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.57.0
Compare Source
Bug Fixes
Features
no-duplicate-type-constituents
rule (#5728) (bc31078)typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.57.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
evanw/esbuild
v0.17.14
Compare Source
Allow the TypeScript 5.0
const
modifier in object type declarations (#3021)The new TypeScript 5.0
const
modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:Implement preliminary lowering for CSS nesting (#1945)
Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!
This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the
:is()
pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support:is()
(e.g. Chrome 88+). You'll need to set esbuild'starget
to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with atarget
which includes older browsers that don't support:is()
.The lowering transformation looks like this:
More complex cases may generate the
:is()
pseudo-class:In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:
Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.
Minification now removes unnecessary
&
CSS nesting selectorsThis release introduces the following CSS minification optimizations:
Minification now removes duplicates from CSS selector lists
This release introduces the following CSS minification optimization:
v0.17.13
Compare Source
Work around an issue with
NODE_PATH
and Go's WebAssembly internals (#3001)Go's WebAssembly implementation returns
EINVAL
instead ofENOTDIR
when using thereaddir
syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encounteringENOTDIR
causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacyNODE_PATH
feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by convertingEINVAL
intoENOTDIR
for thereaddir
syscall.Fix a minification bug with CSS
@layer
rules that have parsing errors (#3016)CSS at-rules require either a
{}
block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate@layer
rules with parsing errors, and empty@layer
rules cannot be removed because they have side effects (@layer
didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard@layer
rules with parsing errors when minifying (the rule@layer c
has a parsing error):Unterminated strings in CSS are no longer an error
The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:
...would be treated the same as:
...because the second declaration (from
font-family
to the semicolon aftercolor: red
) is invalid and is dropped.Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:
eslint/eslint
v8.37.0
Compare Source
Features
b6ab8b2
feat:require-unicode-regexp
add suggestions (#17007) (Josh Goldberg)10022b1
feat: Copy getScope() to SourceCode (#17004) (Nicholas C. Zakas)1665c02
feat: Use plugin metadata for flat config serialization (#16992) (Nicholas C. Zakas)b3634f6
feat: docs license (#17010) (Samuel Roldan)892e6e5
feat: languageOptions.parser must be an object. (#16985) (Nicholas C. Zakas)Bug Fixes
619f3fd
fix: correctly handlenull
default config inRuleTester
(#17023) (Brad Zacher)1fbf118
fix:getFirstToken
/getLastToken
on comment-only node (#16889) (Francesco Trotta)129e252
fix: Fix typo inlogical-assignment-operators
rule description (#17000) (Francesco Trotta)Documentation
75339df
docs: fix typos and missing info in id-match docs (#17029) (Ed Lucas)ec2d830
docs: Fix typos in thesemi
rule docs (#17012) (Andrii Lundiak)e39f28d
docs: add back to top button (#16979) (Tanuj Kanti)721c717
docs: Custom Processors cleanup and expansion (#16838) (Ben Perlmutter)d049f97
docs: 'How ESLint is Maintained' page (#16961) (Ben Perlmutter)5251a92
docs: Describe guard options for guard-for-in (#16986) (alope107)6157d81
docs: Add example to guard-for-in docs. (#16983) (alope107)fd47998
docs: updateArray.prototype.toSorted
specification link (#16982) (Milos Djermanovic)3e1cf6b
docs: Copy edits on Maintain ESLint docs (#16939) (Ben Perlmutter)Chores
c67f299
chore: upgrade @eslint/js@8.37.0 (#17033) (Milos Djermanovic)ee9ddbd
chore: package.json update for @eslint/js release (ESLint Jenkins)dddb475
chore: upgrade @eslint/eslintrc@2.0.2 (#17032) (Milos Djermanovic)522431e
chore: upgrade espree@9.5.1 (#17031) (Milos Djermanovic)f5f9a88
chore: upgrade eslint-visitor-keys@3.4.0 (#17030) (Milos Djermanovic)4dd8d52
ci: bump actions/stale from 7 to 8 (#17026) (dependabot[bot])ad9dd6a
chore: remove duplicate scss, (#17005) (Strek)ada6a3e
ci: unpin Node 19 (#16993) (Milos Djermanovic)c3da975
chore: Remove triage label from template (#16990) (Nicholas C. Zakas)69bc0e2
ci: pin Node 19 to 19.7.0 (#16987) (Milos Djermanovic)prettier/prettier
v2.8.7
Compare Source
diff
Allow multiple decorators on same getter/setter (#14584 by @fisker)
sass/dart-sass
v1.60.0
Compare Source
Add support for the
pi
,e
,infinity
,-infinity
, andNaN
constants incalculations. These will be interpreted as the corresponding numbers.
Add support for unknown constants in calculations. These will be interpreted
as unquoted strings.
Serialize numbers with value
infinity
,-infinity
, andNaN
tocalc()
expressions rather than CSS-invalid identifiers. Numbers with complex units
still can't be serialized.
Configuration
📅 Schedule: Branch creation - "every weekend" (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.