This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
chore(deps): update all non-major dependencies #9737
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:
^5.0.1
->^5.0.2
^18.11.15
->^18.11.17
^0.16.7
->^0.16.9
^8.29.0
->^8.30.0
^7.2.13
->^7.2.14
^5.2.1
->^5.2.2
2.0.0-27850417.cbcd068
->2.0.0-27851797.fc75d47
^1.28.1
->^1.29.0
^3.7.4
->^3.7.5
~4.0.1
->~4.0.2
^4.0.1
->^4.0.2
^1.0.13
->^1.0.14
Release Notes
rollup/plugins
v5.0.2
Compare Source
2022-12-17
Bugfixes
evanw/esbuild
v0.16.9
Compare Source
Update to Unicode 15.0.0
The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 14.0.0 to the newly-released Unicode version 15.0.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.0.0/#Summary for more information about the changes.
Disallow duplicate lexically-declared names in nested blocks and in strict mode
In strict mode or in a nested block, it's supposed to be a syntax error to declare two symbols with the same name unless all duplicate entries are either
function
declarations or allvar
declarations. However, esbuild was overly permissive and allowed this when duplicate entries were eitherfunction
declarations orvar
declarations (even if they were mixed). This check has now been made more restrictive to match the JavaScript specification:Add a type declaration for the new
empty
loader (#2755)I forgot to add this in the previous release. It has now been added.
This fix was contributed by @fz6m.
Add support for the
v
flag in regular expression literalsPeople are currently working on adding a
v
flag to JavaScript regular expresions. You can read more about this flag here: https://v8.dev/features/regexp-v-flag. This release adds support for parsing this flag, so esbuild will now no longer consider regular expression literals with this flag to be a syntax error. If the target is set to something other thanesnext
, esbuild will transform regular expression literals containing this flag into anew RegExp()
constructor call so the resulting code doesn't have a syntax error. This enables you to provide a polyfill forRegExp
that implements thev
flag to get your code to work at run-time. While esbuild doesn't typically adopt proposals until they're already shipping in a real JavaScript run-time, I'm adding it now because a) esbuild's implementation doesn't need to change as the proposal evolves, b) this isn't really new syntax since regular expression literals already have flags, and c) esbuild's implementation is a trivial pass-through anyway.Avoid keeping the name of classes with static
name
propertiesThe
--keep-names
property attempts to preserve the original value of thename
property for functions and classes even when identifiers are renamed by the minifier or to avoid a name collision. This is currently done by generating code to assign a string to thename
property on the function or class object. However, this should not be done for classes with a staticname
property since in that case the explicitly-definedname
property overwrites the automatically-generated class name. With this release, esbuild will now no longer attempt to preserve thename
property for classes with a staticname
property.v0.16.8
Compare Source
Allow plugins to resolve injected files (#2754)
Previously paths passed to the
inject
feature were always interpreted as file system paths. This meant thatonResolve
plugins would not be run for them and esbuild's default path resolver would always be used. This meant that theinject
feature couldn't be used in the browser since the browser doesn't have access to a file system. This release runs paths passed toinject
through esbuild's full path resolution pipeline so plugins now have a chance to handle them usingonResolve
callbacks. This makes it possible to write a plugin that makes esbuild'sinject
work in the browser.Add the
empty
loader (#1541, #2753)The new
empty
loader tells esbuild to pretend that a file is empty. So for example--loader:.css=empty
effectively skips all imports of.css
files in JavaScript so that they aren't included in the bundle, sinceimport "./some-empty-file"
in JavaScript doesn't bundle anything. You can also use theempty
loader to remove asset references in CSS files. For example--loader:.png=empty
causes esbuild to replace asset references such asurl(image.png)
withurl()
so that they are no longer included in the resulting style sheet.Fix
</script>
and</style>
escaping for non-default targets (#2748)The change in version 0.16.0 to give control over
</script>
escaping via--supported:inline-script=false
or--supported:inline-script=true
accidentally broke automatic escaping of</script>
when an explicittarget
setting is specified. This release restores the correct automatic escaping of</script>
(which should not depend on whattarget
is set to).Enable the
exports
field withNODE_PATHS
(#2752)Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the
NODE_PATHS
environment variable. While esbuild supports this too, previously it only supported the oldmain
field path resolution but did not support the newexports
field package resolution. This release makes the path resolution rules the same again for bothnode_modules
directories andNODE_PATHS
directories.eslint/eslint
v8.30.0
Compare Source
Features
075ef2c
feat: add suggestion for no-return-await (#16637) (Daniel Bartholomae)7190d98
feat: update globals (#16654) (Sébastien Règne)Bug Fixes
1a327aa
fix: Ensure flat config unignores work consistently like eslintrc (#16579) (Nicholas C. Zakas)9b8bb72
fix: autofix recursive functions in no-var (#16611) (Milos Djermanovic)Documentation
6a8cd94
docs: Clarify Discord info in issue template config (#16663) (Nicholas C. Zakas)ad44344
docs: CLI documentation standardization (#16563) (Ben Perlmutter)293573e
docs: fix broken line numbers (#16606) (Sam Chen)fa2c64b
docs: use relative links for internal links (#16631) (Percy Ma)75276c9
docs: reorder options in no-unused-vars (#16625) (Milos Djermanovic)7276fe5
docs: Fix anchor in URL (#16628) (Karl Horky)6bef135
docs: don't apply layouts to html formatter example (#16591) (Tanuj Kanti)dfc7ec1
docs: Formatters page updates (#16566) (Ben Perlmutter)8ba124c
docs: update theprefer-const
example (#16607) (Pavel)e6cb05a
docs: fix css leaking (#16603) (Sam Chen)Chores
f2c4737
chore: upgrade @eslint/eslintrc@1.4.0 (#16675) (Milos Djermanovic)ba74253
chore: standardize npm script names per #14827 (#16315) (Patrick McElhaney)0d9af4c
ci: fix npm v9 problem withfile:
(#16664) (Milos Djermanovic)90c9219
refactor: migrate off deprecated function-style rules in all tests (#16618) (Bryan Mishkin)TypeStrong/fork-ts-checker-webpack-plugin
v7.2.14
Compare Source
kaelzhang/node-ignore
v5.2.2
Compare Source
unjs/nitro
v2.0.0-27851797.fc75d47
Compare Source
Microsoft/playwright
v1.29.0
Compare Source
New APIs
New method
route.fetch()
and new optionjson
forroute.fulfill()
:New method
locator.all()
to iterate over all matching elements:Retry blocks of code until all assertions pass:
Read more in our documentation.
Automatically capture full page screenshot on test failure:
Miscellaneous
jsconfig.json
.args
andproxy
forandroidDevice.launchBrowser()
.postData
in methodroute.continue()
now supports serializable values.Browser Versions
This version was also tested against the following stable channels:
rollup/rollup
v3.7.5
Compare Source
2022-12-17
Bug Fixes
RollupWarning.cause
compatible withError.cause
(#4757)Pull Requests
stack
info in cli error (@TrickyPi)vitejs/vite
v4.0.2
Compare Source
toOutputFilePathWithoutRuntime
function (#11367) (8820f75), closes #11367vite optimize
prebundle for dev (#11387) (b4ced0f), closes #11387johnsoncodehk/volar
v1.0.14
Compare Source
vue-tsc-eslint-hook
module to support use eslint in vue-tsc (#2220)volar.vueserver.maxFileSize
(#2186)volar.doctor.checkVueTsc
and disable by default (#2186)volar.vueserver.configFilePath
(#2078)v-bind
(#2105)Special Sponsor
Out Gold Sponsors
Out Silver Sponsors
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.