-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): update patch & minor updates #578
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch-updates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
changed the title
build(deps): update dependency js-beautify to v1.15.1
build(deps): update patch & minor updates
Feb 26, 2024
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
6 times, most recently
from
April 26, 2024 11:44
8787db9
to
1336e10
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
4 times, most recently
from
May 8, 2024 04:41
f446dd2
to
e172c6e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
2 times, most recently
from
May 14, 2024 03:08
f232613
to
3b9d498
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
5 times, most recently
from
May 24, 2024 12:04
8f1a0a1
to
87b50c6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
2 times, most recently
from
May 31, 2024 12:47
0b65082
to
f6b084b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
3 times, most recently
from
June 7, 2024 00:41
b981603
to
f7b2cf3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
4 times, most recently
from
June 19, 2024 19:39
f9ad7c6
to
ddaa9c4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
from
June 24, 2024 22:39
ddaa9c4
to
7b565e0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
5 times, most recently
from
October 25, 2024 07:59
10d828e
to
2251c24
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
6 times, most recently
from
November 1, 2024 15:12
b353621
to
fd8844a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
3 times, most recently
from
November 9, 2024 00:53
bfac46b
to
05caff4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
4 times, most recently
from
November 22, 2024 03:25
cc15c1c
to
f70754e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
3 times, most recently
from
December 2, 2024 09:39
05a4187
to
1f0f449
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
3 times, most recently
from
December 11, 2024 00:32
e4d9d88
to
7024295
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
from
December 12, 2024 19:36
7024295
to
ca534a2
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
2 times, most recently
from
December 21, 2024 19:02
cdea1d3
to
e19f045
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
from
December 27, 2024 07:56
e19f045
to
cc3c024
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch-updates
branch
from
January 1, 2025 18:14
cc3c024
to
90e0b26
Compare
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:
7.25.8
->7.26.0
7.25.8
->7.26.0
^0.23.0
->^0.24.0
^0.12.1
->^0.14.0
11.10.0
->11.11.1
9.1.6
->9.1.7
2.9.1
->2.9.2
6.2.3
->6.2.6
8.4.47
->8.4.49
1.79.5
->1.83.0
Release Notes
babel/babel (@babel/core)
v7.26.0
Compare Source
v7.25.9
Compare Source
🐛 Bug Fix
babel-parser
,babel-template
,babel-types
syntacticPlaceholders
mode (@liuxingbaoyu)babel-helper-compilation-targets
,babel-preset-env
ClassAccessorProperty
to prevent theno-undef
rule (@victorenator)🏠 Internal
babel-helper-transform-fixture-test-runner
🏃♀️ Performance
babel-parser
,babel-types
VISITOR_KEYS
etc. faster to access (@liuxingbaoyu)babel/babel (@babel/preset-env)
v7.26.0
Compare Source
🚀 New Feature
babel-core
,babel-generator
,babel-parser
,babel-plugin-syntax-import-assertions
,babel-plugin-syntax-import-attributes
,babel-preset-env
,babel-standalone
,babel-types
babel-core
babel-compat-data
,babel-plugin-proposal-regexp-modifiers
,babel-plugin-transform-regexp-modifiers
,babel-preset-env
,babel-standalone
transform-regexp-modifiers
topreset-env
(@JLHwung)babel-parser
startIndex
parser option (@DylanPiercey)babel-generator
,babel-parser
,babel-plugin-syntax-flow
babel-helpers
,babel-preset-typescript
,babel-runtime-corejs3
import()
inrewriteImportExtensions
(@liuxingbaoyu)babel-generator
,babel-parser
@babel/generator
(@nicolo-ribaudo)🐛 Bug Fix
babel-core
💅 Polish
babel-plugin-proposal-json-modules
,babel-plugin-transform-json-modules
,babel-standalone
proposal-json-modules
totransform-json-modules
(@nicolo-ribaudo)🏠 Internal
babel-code-frame
,babel-highlight
@babel/highlight
in@babel/code-frame
(@nicolo-ribaudo)babel-generator
,babel-parser
,babel-types
kind
toTSModuleDeclaration
(@liuxingbaoyu)🏃♀️ Performance
babel-helper-module-transforms
,babel-plugin-transform-modules-commonjs
v7.25.9
Compare Source
🐛 Bug Fix
babel-parser
,babel-template
,babel-types
syntacticPlaceholders
mode (@liuxingbaoyu)babel-helper-compilation-targets
,babel-preset-env
ClassAccessorProperty
to prevent theno-undef
rule (@victorenator)🏠 Internal
babel-helper-transform-fixture-test-runner
🏃♀️ Performance
babel-parser
,babel-types
VISITOR_KEYS
etc. faster to access (@liuxingbaoyu)evanw/esbuild (esbuild)
v0.24.2
Compare Source
Fix regression with
--define
andimport.meta
(#4010, #4012, #4013)The previous change in version 0.24.1 to use a more expression-like parser for
define
values to allow quoted property names introduced a regression that removed the ability to use--define:import.meta=...
. Even thoughimport
is normally a keyword that can't be used as an identifier, ES modules special-case theimport.meta
expression to behave like an identifier anyway. This change fixes the regression.This fix was contributed by @sapphi-red.
v0.24.1
Compare Source
Allow
es2024
as a target intsconfig.json
(#4004)TypeScript recently added
es2024
as a compilation target, so esbuild now supports this in thetarget
field oftsconfig.json
files, such as in the following configuration file:As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
This fix was contributed by @billyjanitsch.
Allow automatic semicolon insertion after
get
/set
This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
Allow quoted property names in
--define
and--pure
(#4008)The
define
andpure
API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes--define
and--pure
consistent with--global-name
, which already supported quoted property names. For example, the following is now possible:Note that if you're passing values like this on the command line using esbuild's
--define
flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.Minify empty
try
/catch
/finally
blocks (#4003)With this release, esbuild will now attempt to minify empty
try
blocks:This can sometimes expose additional minification opportunities.
Include
entryPoint
metadata for thecopy
loader (#3985)Almost all entry points already include a
entryPoint
field in theoutputs
map in esbuild's build metadata. However, this wasn't the case for thecopy
loader as that loader is a special-case that doesn't behave like other loaders. This release adds theentryPoint
field in this case.Source mappings may now contain
null
entries (#3310, #3878)With this change, sources that result in an empty source map may now emit a
null
source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now thenull
mapping "resets" the source map so that any lookups into the minified code without any mappings resolves tonull
(which appears as the output file in stack traces) instead of the incorrect source file.This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.
Avoid using the parent directory name for determinism (#3998)
To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named
index.js
(or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all namedindex.js
but have unique directory names).This is problematic when the bundle entry point is named
index.js
and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now useindex
instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild'soutbase
API option, which defaults to the lowest common ancestor of all user-specified entry point paths.Experimental support for esbuild on NetBSD (#3974)
With this release, esbuild now has a published binary executable for NetBSD in the
@esbuild/netbsd-arm64
npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @bsiegert.v0.24.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.23.0
or~0.23.0
. See npm's documentation about semver for more information.Drop support for older platforms (#3902)
This release drops support for the following operating system:
This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.
Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
Fix class field decorators in TypeScript if
useDefineForClassFields
isfalse
(#3913)Setting the
useDefineForClassFields
flag tofalse
intsconfig.json
means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.Avoid incorrect cycle warning with
tsconfig.json
multiple inheritance (#3898)TypeScript 5.0 introduced multiple inheritance for
tsconfig.json
files whereextends
can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release,tsconfig.json
files containing this edge case should work correctly without generating a warning.Handle Yarn Plug'n'Play stack overflow with
tsconfig.json
(#3915)Previously a
tsconfig.json
file thatextends
another file in a package with anexports
map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around more issues with Deno 1.31+ (#3917)
This version of Deno broke the
stdin
andstdout
properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. whenimport.meta.main
istrue
). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.This fix was contributed by @Joshix-1.
ym-project/gulp-esbuild (gulp-esbuild)
v0.14.0
Compare Source
Esbuild moved to peerDependencies. Now you should install
esbuild
yourself:What's Changed
Full Changelog: ym-project/gulp-esbuild@v0.13.0...v0.14.0
v0.13.0
Compare Source
Removed
pipe
flag. Now plugin works with both file system files and virtual files by default.Previous code:
Current code:
What's Changed
Full Changelog: ym-project/gulp-esbuild@v0.12.1...v0.13.0
highlightjs/highlight.js (highlight.js)
v11.11.1
Compare Source
v11.11.0
Compare Source
CAVEATS / POTENTIALLY BREAKING CHANGES
Core Grammars:
\
Josh Goebel$()
expressions aneesh98anchor-name
,aspect-ratio
,backdrop-filter
,container
,margin-trim
,place-content
,scroll-timeline
, ...) BaliBalofile
,args
,dynamic
,record
,required
andscoped
Alvin Joytime
andcoproc
Álvaro Mondéjar|=
operator false positives (as block arguments) Aboobacker MKadd
builtin [h7x4][]or
as builtin instead of literal [h7x4][]'''
string escapes [h7x4][]"
and''
strings [h7x4][]concept
anddefer
to list of Nim keywords Jake LeahyNew Grammars:
Developer Tools:
Themes:
Rosé Pine
theme William WilkinsonCybertopia Cherry
theme Alexandre ZANNICybertopia Dimmer
theme Alexandre ZANNICybertopia Icecap
theme Alexandre ZANNICybertopia Saturated
theme Alexandre ZANNIImprovements:
CONTRIBUTORS
typicode/husky (husky)
v9.1.7
Compare Source
webpack-contrib/mini-css-extract-plugin (mini-css-extract-plugin)
v2.9.2
Compare Source
bcomnes/npm-run-all2 (npm-run-all2)
v6.2.6
Compare Source
Commits
d928f9a
v6.2.5
Compare Source
v6.2.4
Compare Source
Merged
which
command#154
Fixed
which
command#153
postcss/postcss (postcss)
v8.4.49
Compare Source
source.offset
(by @romainmenke).v8.4.48
Compare Source
sass/dart-sass (sass)
v1.83.0
Compare Source
v1.82.0
Compare Source
Command-Line Interface
Improve
--watch
mode reliability when making multiple changes at once, suchas checking out a different Git branch.
Parse the
calc-size()
function as a calculation now that it's supported insome browsers.
Dart API
SassCalculation.calcSize()
function.v1.81.1
Compare Source
v1.81.0
Compare Source
Fix a few cases where deprecation warnings weren't being emitted for global
built-in functions whose names overlap with CSS calculations.
Add support for the CSS
round()
calculation with a single argument, as longas that argument might be a unitless number.
v1.80.7
Compare Source
Embedded Host
0
asundefined
for thegreen
andblue
channels in theLegacyColor
constructor.v1.80.6
Compare Source
Command-Line Interface
@parcel/watcher
an optional dependency so this can still be installedon operating systems where it's unavailable.
v1.80.5
Compare Source
Embedded Host
@import
deprecations when using an importer with thelegacy API.
v1.80.4
Compare Source
v1.80.3
Compare Source
Fix a bug where
@import url("...")
would crash in plain CSS files.Improve consistency of how warnings are emitted by different parts of the
compiler. This should result in minimal user-visible changes, but different
types of warnings should now respond more reliably to flags like
--quiet
,--verbose
, and--silence-deprecation
.v1.80.2
Compare Source
plain-CSS
invert()
function.v1.80.1
Compare Source
v1.80.0
Compare Source
@import
is now officially deprecated, as are global built-in functions thatare available within built-in modules. See the Sass blog post for more
details on the deprecation process.
Embedded Host
emitted when using a custom importer with the legacy API.
v1.79.6
Compare Source
Fix a bug where Sass would add an extra
*/
after loud comments withwhitespace after an explicit
*/
in the indented syntax.Potentially breaking bug fix: Adding text after an explicit
*/
in theindented syntax is now an error, rather than silently generating invalid CSS.
Embedded Host
SassBoolean
type.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 was generated by Mend Renovate. View the repository job log.