chore(deps): update all non-major dependencies #1567
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:
^25.0.3
->^25.0.4
^5.0.2
->^5.0.3
^0.23.0
->^0.23.1
^0.19.0
->^0.19.2
^8.46.0
->^8.47.0
^1.2.2
->^1.3.0
^1.1.2
->^1.1.3
^6.4.2
->^6.4.5
8.6.11
->8.6.12
^3.27.2
->^3.28.0
Release Notes
rollup/plugins (@rollup/plugin-commonjs)
v25.0.4
Compare Source
2023-08-11
Updates
rollup/plugins (@rollup/pluginutils)
v5.0.3
Compare Source
2023-08-13
Bugfixes
vercel/nft (@vercel/nft)
v0.23.1
Compare Source
Bug Fixes
builtinModules
frommodule
(#358) (bcb71fd)evanw/esbuild (esbuild)
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.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)unjs/listhen (listhen)
v1.3.0
Compare Source
compare changes
🚀 Enhancements
qr
andpublicURL
options and--qr
,--no-qr
, and--public-url
cli flags (#97)public
option and--host
flag to disable network expose in development by default (#98)https.*
options (#93)unjs/untun
andcloudflared
(experimental) (#102)🔥 Performance
@parcel/watcher
whenever available (#95)🩹 Fixes
node_modules
first (#94)💅 Refactors
🏡 Chore
✅ Tests
❤️ Contributors
unjs/ohash (ohash)
v1.1.3
Compare Source
compare changes
🔥 Performance
isNativeFunction
check (#30)💅 Refactors
📖 Documentation
objectHash()
(#43)🏡 Chore
❤️ Contributors
drwpow/openapi-typescript (openapi-typescript)
v6.4.5
Compare Source
Patch Changes
#1280
50441d0
Thanks @pvanagtmaal! - Fix invalid typescript for empty request bodies, fix headers being left out when response body is omitted#1289
7f452fa
Thanks @adamschoenemann! - Fixed a bug where references to types with discriminators with implicit mappings would generate incorrect typesv6.4.4
Compare Source
Patch Changes
ebd31ff
Thanks @pvanagtmaal! - Refactor CLI path handling, fixing several bugsv6.4.3
Compare Source
Patch Changes
8a9d8ed
Thanks @drwpow! - Fix oneOf handling with empty object parent typepnpm/pnpm (pnpm)
v8.6.12
Compare Source
Patch Changes
pnpm patch
should work correctly whenshared-workspace-file
is set tofalse
#6885.pnpm env use
should retry deleting the previous Node.js executable #6587.pnpm dlx
should not print an error stack when the underlying script execution fails #6698.pnpm install --frozen-lockfile --lockfile-only
should fail if the lockfile is not up to date with thepackage.json
files #6913.Our Gold Sponsors
Our Silver Sponsors
rollup/rollup (rollup)
v3.28.0
Compare Source
2023-08-09
Features
preliminaryFileName
to generated chunks containing the file name placeholder (#5086)Bug Fixes
code
property of rendered modules in the output readonly (#5091)Pull Requests
preliminaryFileName
toOutputChunk
(@lsdsjy)Configuration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 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.