chore(deps): update all non-major dependencies #360
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
f26af3e
to
4825bbd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
4825bbd
to
def46ff
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
def46ff
to
2a7a621
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
2a7a621
to
6ece1bd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
6ece1bd
to
f63a8cd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
f63a8cd
to
40a5e14
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
40a5e14
to
3b8789d
Compare
WinterYukky
pushed a commit
to WinterYukky/nitro
that referenced
this pull request
Nov 1, 2022
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
1.1.0-beta.16->1.1.0-beta.20^0.14.49->^0.14.50^0.7.10->^0.7.127.5.2->7.6.0^2.77.0->^2.77.1^0.6.0->^0.6.3^0.18.1->^0.19.1Release Notes
vercel/edge-runtime
v1.1.0-beta.20Compare Source
v1.1.0-beta.19Compare Source
v1.1.0-beta.18Compare Source
v1.1.0-beta.17Compare Source
evanw/esbuild
v0.14.50Compare Source
Emit
namesin source maps (#1296)The source map specification includes an optional
namesfield that can associate an identifier with a mapping entry. This can be used to record the original name for an identifier, which is useful if the identifier was renamed to something else in the generated code. When esbuild was originally written, this field wasn't widely used, but now there are some debuggers that make use of it to provide better debugging of minified code. With this release, esbuild now includes anamesfield in the source maps that it generates. To save space, the original name is only recorded when it's different from the final name.Update parser for arrow functions with initial default type parameters in
.tsxfiles (#2410)TypeScript 4.6 introduced a change to the parsing of JSX syntax in
.tsxfiles. Now a<token followed by an identifier and then a=token is parsed as an arrow function with a default type parameter instead of as a JSX element. This release updates esbuild's parser to match TypeScript's parser.Fix an accidental infinite loop with
--definesubstitution (#2407)This is a fix for a regression that was introduced in esbuild version 0.14.44 where certain
--definesubstitutions could result in esbuild crashing with a stack overflow. The problem was an incorrect fix for #2292. The fix merged the code paths for--defineand--jsx-factoryrewriting since the value substitution is now the same for both. However, doing this accidentally made--definesubstitution recursive since the JSX factory needs to be able to match against--definesubstitutions to integrate with the--injectfeature. The fix is to only do one additional level of matching against define substitutions, and to only do this for JSX factories. Now these cases are able to build successfully without a stack overflow.Include the "public path" value in hashes (#2403)
The
--public-path=configuration value affects the paths that esbuild uses to reference files from other files and is used in various situations such as cross-chunk imports in JS and references to asset files from CSS files. However, it wasn't included in the hash calculations used for file names due to an oversight. This meant that changing the public path setting incorrectly didn't result in the hashes in file names changing even though the contents of the files changed. This release fixes the issue by including a hash of the public path in all non-asset output files.Fix a cross-platform consistency bug (#2383)
Previously esbuild would minify
0xFFFF_FFFF_FFFF_FFFFas0xffffffffffffffff(18 bytes) on arm64 chips and as18446744073709552e3(19 bytes) on x86_64 chips. The reason was that the number was converted to a 64-bit unsigned integer internally for printing as hexadecimal, the 64-bit floating-point number0xFFFF_FFFF_FFFF_FFFFis actually0x1_0000_0000_0000_0180(i.e. it's rounded up, not down), and convertingfloat64touint64is implementation-dependent in Go when the input is out of bounds. This was fixed by changing the upper limit for which esbuild uses hexadecimal numbers during minification to0xFFFF_FFFF_FFFF_F800, which is the next representable 64-bit floating-point number below0x1_0000_0000_0000_0180, and which fits in auint64. As a result, esbuild will now consistently never minify0xFFFF_FFFF_FFFF_FFFFas0xffffffffffffffffanymore, which means the output should now be consistent across platforms.Fix a hang with the synchronous API when the package is corrupted (#2396)
An error message is already thrown when the esbuild package is corrupted and esbuild can't be run. However, if you are using a synchronous call in the JavaScript API in worker mode, esbuild will use a child worker to initialize esbuild once so that the overhead of initializing esbuild can be amortized across multiple synchronous API calls. However, errors thrown during initialization weren't being propagated correctly which resulted in a hang while the main thread waited forever for the child worker to finish initializing. With this release, initialization errors are now propagated correctly so calling a synchronous API call when the package is corrupted should now result in an error instead of a hang.
Fix
tsconfig.jsonfiles that collide with directory names (#2411)TypeScript lets you write
tsconfig.jsonfiles withextendsclauses that refer to another config file using an implicit.jsonfile extension. However, if the config file without the.jsonextension existed as a directory name, esbuild and TypeScript had different behavior. TypeScript ignores the directory and continues looking for the config file by adding the.jsonextension while esbuild previously terminated the search and then failed to load the config file (because it's a directory). With this release, esbuild will now ignore exact matches when resolvingextendsfields intsconfig.jsonfiles if the exact match results in a directory.Add
platformto the transform API (#2362)The
platformoption is mainly relevant for bundling because it mostly affects path resolution (e.g. activating the"browser"field inpackage.jsonfiles), so it was previously only available for the build API. With this release, it has additionally be made available for the transform API for a single reason: you can now set--platform=nodewhen transforming a string so that esbuild will add export annotations for node, which is only relevant when--format=cjsis also present.This has to do with an implementation detail of node that parses the AST of CommonJS files to discover named exports when importing CommonJS from ESM. However, this new addition to esbuild's API is of questionable usefulness. Node's loader API (the main use case for using esbuild's transform API like this) actually bypasses the content returned from the loader and parses the AST that's present on the file system, so you won't actually be able to use esbuild's API for this. See the linked issue for more information.
unjs/h3
v0.7.12Compare Source
v0.7.11Compare Source
pnpm/pnpm
v7.6.0Compare Source
Minor Changes
A new setting supported:
prefer-symlinked-executables. Whentrue, pnpm will create symlinks to executables innode_modules/.bininstead of command shims (but on POSIX systems only).This setting is
trueby default whennode-linkeris set tohoisted.Related issue: #4782.
When
lockfile-include-tarball-urlis set totrue, every entry inpnpm-lock.yamlwill contain the full URL to the package's tarball #5054.Patch Changes
pnpm deployshould include all dependencies by default #5035.Don't print warnings about file verifications. Just print info messages instead.
pnpm publish --helpshould print the--recursiveand--filteroptions #5019.It should be possible to run exec/run/dlx with the
--use-node-versionoption.pnpm deployshould not modify the lockfile #5071pnpm deployshould not fail in CI #5071When
auto-install-peersis set totrue, automatically install direct peer dependencies #5028.So if your project the next manifest:
{ "dependencies": { "lodash": "^4.17.21" }, "peerDependencies": { "react": "^18.2.0" } }pnpm will install both lodash and react as a regular dependencies.
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.2...v7.6.0
rollup/rollup
v2.77.1Compare Source
2022-07-26
Bug Fixes
Pull Requests
unjs/unimport
v0.6.3Compare Source
v0.6.2Compare Source
v0.6.1Compare Source
vitest-dev/vitest
v0.19.1Compare Source
🚀 Features
View changes on GitHub
v0.19.0Compare Source
🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
View changes on GitHub
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.