chore(deps): update all non-major dependencies #25
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.4.2
0.18.8
->0.18.14
8.43.0
->8.45.0
15.6.0
->15.9.0
18.16.1
->18.17.0
Release Notes
evanw/esbuild (esbuild)
v0.18.14
Compare Source
Implement local CSS names (#20)
This release introduces two new loaders called
global-css
andlocal-css
and two new pseudo-class selectors:local()
and:global()
. This is a partial implementation of the popular CSS modules approach for avoiding unintentional name collisions in CSS. I'm not calling this feature "CSS modules" because although some people in the community call it that, other people in the community have started using "CSS modules" to refer to something completely different and now CSS modules is an overloaded term.Here's how this new local CSS name feature works with esbuild:
Identifiers that look like
.className
and#idName
are global with theglobal-css
loader and local with thelocal-css
loader. Global identifiers are the same across all files (the way CSS normally works) but local identifiers are different between different files. If two separate CSS files use the same local identifier.button
, esbuild will automatically rename one of them so that they don't collide. This is analogous to how esbuild automatically renames JS local variables with the same name in separate JS files to avoid name collisions.It only makes sense to use local CSS names with esbuild when you are also using esbuild's bundler to bundle JS files that import CSS files. When you do that, esbuild will generate one export for each local name in the CSS file. The JS code can import these names and use them when constructing HTML DOM. For example:
When you bundle this with
esbuild app.js --bundle --loader:.css=local-css --outdir=out
you'll now get this (notice how the local CSS nameouterShell
has been renamed):This feature only makes sense to use when bundling is enabled both because your code needs to
import
the renamed local names so that it can use them, and because esbuild needs to be able to process all CSS files containing local names in a single bundling operation so that it can successfully rename conflicting local names to avoid collisions.If you are in a global CSS file (with the
global-css
loader) you can create a local name using:local()
, and if you are in a local CSS file (with thelocal-css
loader) you can create a global name with:global()
. So the choice of theglobal-css
loader vs. thelocal-css
loader just sets the default behavior for identifiers, but you can override it on a case-by-case basis as necessary. For example:Processing this CSS file with esbuild with either the
global-css
orlocal-css
loader will result in something like this:The names that esbuild generates for local CSS names are an implementation detail and are not intended to be hard-coded anywhere. The only way you should be referencing the local CSS names in your JS or HTML is with an
import
statement in JS that is bundled with esbuild, as demonstrated above. For example, when--minify
is enabled esbuild will use a different name generation algorithm which generates names that are as short as possible (analogous to how esbuild minifies local identifiers in JS).You can easily use both global CSS files and local CSS files simultaneously if you give them different file extensions. For example, you could pass
--loader:.css=global-css
and--loader:.module.css=local-css
to esbuild so that.css
files still use global names by default but.module.css
files use local names by default.Keep in mind that the
css
loader is different than theglobal-css
loader. The:local
and:global
annotations are not enabled with thecss
loader and will be passed through unchanged. This allows you to have the option of using esbuild to process CSS containing while preserving these annotations. It also means that local CSS names are disabled by default for now (since thecss
loader is currently the default for CSS files). The:local
and:global
syntax may be enabled by default in a future release.Note that esbuild's implementation does not currently have feature parity with other implementations of modular CSS in similar tools. This is only a preliminary release with a partial implementation that includes some basic behavior to get the process started. Additional behavior may be added in future releases. In particular, this release does not implement:
composes
pragma@container
,@counter-style
, etc.Issue #20 (the issue for this feature) is esbuild's most-upvoted issue! While this release still leaves that issue open, it's an important first step in that direction.
Parse
:is
,:has
,:not
, and:where
in CSSWith this release, esbuild will now parse the contents of these pseudo-class selectors as a selector list. This means you will now get syntax warnings within these selectors for invalid selector syntax. It also means that esbuild's CSS nesting transform behaves slightly differently than before because esbuild is now operating on an AST instead of a token stream. For example:
v0.18.13
Compare Source
Add the
--drop-labels=
option (#2398)If you want to conditionally disable some development-only code and have it not be present in the final production bundle, right now the most straightforward way of doing this is to use the
--define:
flag along with a specially-named global variable. For example, consider the following code:You can build this for development and production like this:
esbuild --define:DEV=true
esbuild --define:DEV=false
One drawback of this approach is that the resulting code crashes if you don't provide a value for
DEV
with--define:
. In practice this isn't that big of a problem, and there are also various ways to work around this.However, another approach that avoids this drawback is to use JavaScript label statements instead. That's what the
--drop-labels=
flag implements. For example, consider the following code:With this release, you can now build this for development and production like this:
esbuild
esbuild --drop-labels=DEV
This means that code containing optional development-only checks can now be written such that it's safe to run without any additional configuration. The
--drop-labels=
flag takes comma-separated list of multiple label names to drop.Avoid causing
unhandledRejection
during shutdown (#3219)All pending esbuild JavaScript API calls are supposed to fail if esbuild's underlying child process is unexpectedly terminated. This can happen if
SIGINT
is sent to the parentnode
process with Ctrl+C, for example. Previously doing this could also cause an unhandled promise rejection when esbuild attempted to communicate this failure to its own child process that no longer exists. This release now swallows this communication failure, which should prevent this internal unhandled promise rejection. This change means that you can now use esbuild's JavaScript API with a customSIGINT
handler that extends the lifetime of thenode
process without esbuild's internals causing an early exit due to an unhandled promise rejection.Update browser compatibility table scripts
The scripts that esbuild uses to compile its internal browser compatibility table have been overhauled. Briefly:
caniuse-lite
and@mdn/browser-compat-data
as new data sources (replacing manually-copied information)This change means it's now much easier to keep esbuild's internal compatibility tables up to date. You can review the table changes here if you need to debug something about this change:
v0.18.12
Compare Source
Fix a panic with
const enum
inside parentheses (#3205)This release fixes an edge case where esbuild could potentially panic if a TypeScript
const enum
statement was used inside of a parenthesized expression and was followed by certain other scope-related statements. Here's a minimal example that triggers this edge case:Allow a newline in the middle of TypeScript
export type
statement (#3225)Previously esbuild incorrectly rejected the following valid TypeScript code:
Code that uses a newline after
export type
is now allowed starting with this release.Fix cross-module inlining of string enums (#3210)
A refactoring typo in version 0.18.9 accidentally introduced a regression with cross-module inlining of string enums when combined with computed property accesses. This regression has been fixed.
Rewrite
.js
to.ts
inside packages withexports
(#3201)Packages with the
exports
field are supposed to disable node's path resolution behavior that allows you to import a file with a different extension than the one in the source code (for example, importingfoo/bar
to getfoo/bar.js
). And TypeScript has behavior where you can import a non-existent.js
file and you will get the.ts
file instead. Previously the presence of theexports
field caused esbuild to disable all extension manipulation stuff which included both node's implicit file extension searching and TypeScript's file extension swapping. However, TypeScript appears to always apply file extension swapping even in this case. So with this release, esbuild will now rewrite.js
to.ts
even inside packages withexports
.Fix a redirect edge case in esbuild's development server (#3208)
The development server canonicalizes directory URLs by adding a trailing slash. For example, visiting
/about
redirects to/about/
if/about/index.html
would be served. However, if the requested path begins with two slashes, then the redirect incorrectly turned into a protocol-relative URL. For example, visiting//about
redirected to//about/
which the browser turns intohttp://about/
. This release fixes the bug by canonicalizing the URL path when doing this redirect.v0.18.11
Compare Source
Fix a TypeScript code generation edge case (#3199)
This release fixes a regression in version 0.18.4 where using a TypeScript
namespace
that exports aclass
declaration combined with--keep-names
and a--target
ofes2021
or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment toX2._Y
vs.X2.Y
):v0.18.10
Compare Source
Fix a tree-shaking bug that removed side effects (#3195)
This fixes a regression in version 0.18.4 where combining
--minify-syntax
with--keep-names
could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because--keep-names
generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then--minify-syntax
could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.Fix an incorrect warning about CSS nesting (#3197)
A warning is currently generated when transforming nested CSS to a browser that doesn't support
:is()
because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as@top-left
within@page
. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.v0.18.9
Compare Source
Fix
await using
declarations insideasync
generator functionsI forgot about the new
await using
declarations when implementing lowering forasync
generator functions in the previous release. This change fixes the transformation ofawait using
declarations when they are inside loweredasync
generator functions:Insert some prefixed CSS properties when appropriate (#3122)
With this release, esbuild will now insert prefixed CSS properties in certain cases when the
target
setting includes browsers that require a certain prefix. This is currently done for the following properties:appearance: *;
=>-webkit-appearance: *; -moz-appearance: *;
backdrop-filter: *;
=>-webkit-backdrop-filter: *;
background-clip: text
=>-webkit-background-clip: text;
box-decoration-break: *;
=>-webkit-box-decoration-break: *;
clip-path: *;
=>-webkit-clip-path: *;
font-kerning: *;
=>-webkit-font-kerning: *;
hyphens: *;
=>-webkit-hyphens: *;
initial-letter: *;
=>-webkit-initial-letter: *;
mask-image: *;
=>-webkit-mask-image: *;
mask-origin: *;
=>-webkit-mask-origin: *;
mask-position: *;
=>-webkit-mask-position: *;
mask-repeat: *;
=>-webkit-mask-repeat: *;
mask-size: *;
=>-webkit-mask-size: *;
position: sticky;
=>position: -webkit-sticky;
print-color-adjust: *;
=>-webkit-print-color-adjust: *;
tab-size: *;
=>-moz-tab-size: *; -o-tab-size: *;
text-decoration-color: *;
=>-webkit-text-decoration-color: *; -moz-text-decoration-color: *;
text-decoration-line: *;
=>-webkit-text-decoration-line: *; -moz-text-decoration-line: *;
text-decoration-skip: *;
=>-webkit-text-decoration-skip: *;
text-emphasis-color: *;
=>-webkit-text-emphasis-color: *;
text-emphasis-position: *;
=>-webkit-text-emphasis-position: *;
text-emphasis-style: *;
=>-webkit-text-emphasis-style: *;
text-orientation: *;
=>-webkit-text-orientation: *;
text-size-adjust: *;
=>-webkit-text-size-adjust: *; -ms-text-size-adjust: *;
user-select: *;
=>-webkit-user-select: *; -moz-user-select: *; -ms-user-select: *;
Here is an example:
Browser compatibility data was sourced from the tables on https://caniuse.com. Support for more CSS properties can be added in the future as appropriate.
Fix an obscure identifier minification bug (#2809)
Function declarations in nested scopes behave differently depending on whether or not
"use strict"
is present. To avoid generating code that behaves differently depending on whether strict mode is enabled or not, esbuild transforms nested function declarations into variable declarations. However, there was a bug where the generated variable name was not being recorded as declared internally, which meant that it wasn't being renamed correctly by the minifier and could cause a name collision. This bug has been fixed:Fix a bug in esbuild's compatibility table script (#3179)
Setting esbuild's
target
to a specific JavaScript engine tells esbuild to use the JavaScript syntax feature compatibility data from https://kangax.github.io/compat-table/es6/ for that engine to determine which syntax features to allow. However, esbuild's script that builds this internal compatibility table had a bug that incorrectly ignores tests for engines that still have outstanding implementation bugs which were never fixed. This change fixes this bug with the script.The only case where this changed the information in esbuild's internal compatibility table is that the
hermes
target is marked as no longer supporting destructuring. This is because there is a failing destructuring-related test for Hermes on https://kangax.github.io/compat-table/es6/. If you want to use destructuring with Hermes anyway, you can pass--supported:destructuring=true
to esbuild to override thehermes
target and force esbuild to accept this syntax.This fix was contributed by @ArrayZoneYour.
eslint/eslint (eslint)
v8.45.0
Compare Source
Features
cdd063c
feat: Expose LegacyESLint in unsupported API (#17341) (Nicholas C. Zakas)d34abe5
feat: fix indent rule for else-if (#17318) (Milos Djermanovic)Bug Fixes
b79b6fb
fix: Fix suggestion message inno-useless-escape
(#17339) (Francesco Trotta)c667055
fix: provide uniquefix
andfix.range
objects in lint messages (#17332) (Milos Djermanovic)Documentation
89f3225
docs: add playground links to correct and incorrect code blocks (#17306) (Josh Goldberg ✨)f8892b5
docs: Expand rule option schema docs (#17198) (Matt Wilkinson)8bcbf11
docs: Config Migration Guide (#17230) (Ben Perlmutter)bb30908
docs: Update README (GitHub Actions Bot)84d243b
docs: Update README (GitHub Actions Bot)b762632
docs: Update README (GitHub Actions Bot)138c096
docs: add more prefer-destructuring examples with array destructuring (#17330) (Milos Djermanovic)1fc50a8
docs:max-len
rulecode
andtabWidth
as positional arguments (#17331) (Jesús Leganés-Combarro)Chores
68f63d7
chore: package.json update for @eslint/js release (ESLint Jenkins)5ca9b4d
chore: update eslint-config-eslint exports (#17336) (Milos Djermanovic)7bf2e86
chore: remove unused dependencies (#17352) (Percy Ma)c6f8cd0
chore: RemovedefaultIgnores
from FlatESLint private members (#17349) (Francesco Trotta)0052374
chore: move jsdoc settings to eslint-config-eslint (#17338) (唯然)v8.44.0
Compare Source
Features
1766771
feat: addes2023
andes2024
environments (#17328) (Milos Djermanovic)4c50400
feat: addecmaVersion: 2024
, regexpv
flag parsing (#17324) (Milos Djermanovic)4d411e4
feat: add ternaryOperandBinaryExpressions option to no-extra-parens rule (#17270) (Percy Ma)c8b1f4d
feat: MoveparserServices
toSourceCode
(#17311) (Milos Djermanovic)ef6e24e
feat: treat unknown nodes as having the lowest precedence (#17302) (Brad Zacher)1866e1d
feat: allow flat config files to export a Promise (#17301) (Milos Djermanovic)Bug Fixes
a36bcb6
fix: no-unused-vars false positive with logical assignment operators (#17320) (Gweesin Chan)7620b89
fix: Removeno-unused-labels
autofix before potential directives (#17314) (Francesco Trotta)391ed38
fix: Removeno-extra-semi
autofix before potential directives (#17297) (Francesco Trotta)Documentation
526e911
docs: resubmit pr 17115 doc changes (#17291) (唯然)e1314bf
docs: Integration section and tutorial (#17132) (Ben Perlmutter)19a8c5d
docs: Update README (GitHub Actions Bot)Chores
49e46ed
chore: upgrade @eslint/js@8.44.0 (#17329) (Milos Djermanovic)a1cb642
chore: package.json update for @eslint/js release (ESLint Jenkins)840a264
test: More test cases for no-case-declarations (#17315) (Elian Cordoba)e6e74f9
chore: package.json update for eslint-config-eslint release (ESLint Jenkins)eb3d794
chore: upgrade semver@7.5.3 (#17323) (Ziyad El Abid)cf88439
chore: upgrade optionator@0.9.3 (#17319) (Milos Djermanovic)9718a97
refactor: remove unnecessary code inflat-eslint.js
(#17308) (Milos Djermanovic)f82e56e
perf: various performance improvements (#17135) (moonlightaria)da81e66
chore: update eslint-plugin-jsdoc to 46.2.5 (#17245) (唯然)b991640
chore: switch eslint-config-eslint to the flat format (#17247) (唯然)netlify/cli (netlify-cli)
v15.9.0
Compare Source
Features
Bug Fixes
v15.8.1
Compare Source
Bug Fixes
v15.8.0
Compare Source
Features
is_secret
on environment variables (#5824) (77d4575)Bug Fixes
v15.7.0
Compare Source
Features
Bug Fixes
nodejs/node (node)
v18.17.0
: 2023-07-18, Version 18.17.0 'Hydrogen' (LTS), @danielleadamsCompare Source
Notable Changes
Ada 2.0
Node.js v18.17.0 comes with the latest version of the URL parser, Ada. This update brings significant performance improvements
to URL parsing, including enhancements to the url.domainToASCII and url.domainToUnicode functions in node:url.
Ada 2.0 has been integrated into the Node.js codebase, ensuring that all parts of the application can benefit from the
improved performance. Additionally, Ada 2.0 features a significant performance boost over its predecessor, Ada 1.0.4,
while also eliminating the need for the ICU requirement for URL hostname parsing.
Contributed by Yagiz Nizipli and Daniel Lemire in #47339
Web Crypto API
Web Crypto API functions' arguments are now coerced and validated as per their WebIDL definitions like in other Web Crypto API implementations.
This further improves interoperability with other implementations of Web Crypto API.
Contributed by Filip Skokan in #46067
test
(Chemi Atlow) #47909Commits
2ba08ac002
] - benchmark: usecluster.isPrimary
instead ofcluster.isMaster
(Deokjin Kim) #4800260ca69d96c
] - benchmark: add eventtarget creation bench (Rafael Gonzaga) #47774d8233d96bb
] - benchmark: add a benchmark fordefaultResolve
(Antoine du Hamel) #47543a1aabb6912
] - benchmark: fix invalid requirementsURL (Deokjin Kim) #47378394c61caf9
] - bootstrap: support namespaced builtins in snapshot scripts (Joyee Cheung) #474670165a765a0
] - bootstrap: do not expand process.argv[1] for snapshot entry points (Joyee Cheung) #47466cca557cdd9
] - buffer: combine checking range of sourceStart inbuf.copy
(Deokjin Kim) #477584c69be467c
] - buffer: use private properties for brand checks in File (Matthew Aitken) #47154d002f9b6e2
] - build: revert unkonwn ruff selector (Moshe Atlow) #4875393f77cb762
] - build: set v8_enable_webassembly=false when lite mode is enabled (Cheng Shao) #482481662e894f3
] - build: add action to close stale PRs (Michael Dawson) #480515ca437b288
] - build: use pathlib for paths (Mohammed Keyvanzadeh) #4758172443bc54b
] - build: refactor configure.py (Mohammed Keyvanzadeh) #47667d4eecb5be9
] - build: add devcontainer configuration (Tierney Cyren) #40825803ed41144
] - build: bump ossf/scorecard-action from 2.1.2 to 2.1.3 (dependabot[bot]) #4736748468c4413
] - build: replace Python linter flake8 with ruff (Christian Clauss) #475193ceb2c4387
] - build: add node-core-utils to setup (Jiawen Geng) #47442fdc59b8e14
] - build: bump github/codeql-action from 2.2.6 to 2.2.9 (dependabot[bot]) #473663924893023
] - build: update stale action from v7 to v8 (Rich Trott) #47357753185c5b0
] - build: remove Python pip--no-user
option (Christian Clauss) #4737267af0a6a2b
] - build: avoid usage of pipes library (Mohammed Keyvanzadeh) #47271db910dd6b2
] - build, deps, tools: avoid excessive LTO (Konstantin Demin) #4731335d1def891
] - child_process: use signal.reason in child process abort (Debadree Chatterjee) #478177692d2e7b9
] - cluster: use ObjectPrototypeHasOwnProperty (Daeyeon Jeong) #481417617772762
] - crypto: use openssl's own memory BIOs in crypto_context.cc (GauriSpears) #471608cabfe7c6e
] - crypto: fix setEngine() when OPENSSL_NO_ENGINE set (Tobias Nießen) #47977de1338da05
] - crypto: fix webcrypto private/secret import with empty usages (Filip Skokan) #4787727a696fda9
] - crypto: update root certificates to NSS 3.89 (Node.js GitHub Bot) #47659e2292f936e
] - crypto: remove INT_MAX restriction in randomBytes (Tobias Nießen) #47559a5f214c00c
] - crypto: replace THROW with CHECK for scrypt keylen (Tobias Nießen) #47407dd42214fd4
] - crypto: unify validation of checkPrime checks (Tobias Nießen) #4716576e4d12fb3
] - crypto: re-add padding for AES-KW wrapped JWKs (Filip Skokan) #465639d894c17dd
] - crypto: use WebIDL converters in WebCryptoAPI (Filip Skokan) #460676f3a8b45a5
] - deps: update ada to 2.5.0 (Node.js GitHub Bot) #48223075b6db919
] - deps: update ada to 2.4.2 (Node.js GitHub Bot) #48092a4ee1f652c
] - deps: update ada to 2.4.1 (Node.js GitHub Bot) #4803681b514d3f0
] - deps: update ada to 2.4.0 (Node.js GitHub Bot) #47922575ddf694f
] - deps: update ada to 2.3.1 (Node.js GitHub Bot) #478932d03d5f458
] - deps: update ada to 2.3.0 (Node.js GitHub Bot) #4773742e690f2d5
] - deps: update ada to 2.2.0 (Node.js GitHub Bot) #4767808dd271521
] - deps: update ada to 2.1.0 (Node.js GitHub Bot) #4759896c50ba71f
] - deps: update ada to 2.0.0 (Node.js GitHub Bot) #473394d1c38b758
] - deps: update zlib to337322d
(Node.js GitHub Bot) #4821874206b2549
] - deps: update histogram 0.11.8 (Marco Ippolito) #47742fbb4b3775d
] - deps: update histogram to 0.11.7 (Marco Ippolito) #47742e88c079022
] - deps: update simdutf to 3.2.12 (Node.js GitHub Bot) #4811848bd1248b9
] - deps: update minimatch to 9.0.1 (Node.js GitHub Bot) #48094d4572d31fa
] - deps: update corepack to 0.18.0 (Node.js GitHub Bot) #480918090d29dc4
] - deps: update uvwasi to 0.0.18 (Node.js GitHub Bot) #47866169c8eea2e
] - deps: update uvwasi to 0.0.17 (Node.js GitHub Bot) #478666acbb23380
] - deps: upgrade npm to 9.6.7 (npm team) #48062e8f2c0a58b
] - deps: update undici to 5.22.1 (Node.js GitHub Bot) #47994Configuration
📅 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.