-
-
Notifications
You must be signed in to change notification settings - Fork 1
Update Patch updates (patch) #107
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
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details:
|
commit: |
6413c76
to
37cc98a
Compare
3b16a4c
to
38ff525
Compare
e64fb2e
to
0c431df
Compare
89f4a39
to
0d57661
Compare
eaa1348
to
d862418
Compare
32f5829
to
0435d11
Compare
Review the following changes in direct dependencies. Learn more about Socket for GitHub ↗.
|
8eccc6f
to
326aa3a
Compare
9917dd2
to
7c1aebb
Compare
71a3059
to
bfcba94
Compare
Signed-off-by: Renovate Bot <[email protected]>
bfcba94
to
1af2e58
Compare
This PR contains the following updates:
0.10.0
->0.10.1
>=2.2.4
->>=2.2.7
^0.25.0
->^0.25.2
1.29.1
->1.29.3
4.0.6
->4.0.7
^0.0.40
->^0.0.42
^0.3.8
->^0.3.11
>=4.2.0
->>=4.2.10
>=0.7.0
->>=0.7.3
0.7.2
->0.7.3
Release Notes
bombshell-dev/clack (@clack/prompts)
v0.10.1
Compare Source
Patch Changes
11a5dc1
: Fixes multiselect only shows hints on the first item in the options list. Now correctly shows hints for all selected options with hint property.30aa7ed
: Adds a newselectableGroups
boolean to the group multi-select prompt. UsingselectableGroups: false
will disable the ability to select a top-level group, but still allow every child to be selected individually.30aa7ed
]5dfce8a
]f574297
]wanasit/chrono (chrono-node@<2.2.4)
v2.2.7
Compare Source
f036345
77fbd83
dde6103
b9c02f5
v2.2.6
Compare Source
cdfb6bc
053cc8f
6a52cf3
v2.2.5
Compare Source
38cbefb
fab8f51
ac08a8c
evanw/esbuild (esbuild)
v0.25.2
Compare Source
Support flags in regular expressions for the API (#4121)
The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the
filter
option. Internally these are translated into Go regular expressions. However, this translation previously ignored theflags
property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression/\.[jt]sx?$/i
is turned into the Go regular expression`(?i)\.[jt]sx?$`
internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with thei
flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.Fix node-specific annotations for string literal export names (#4100)
When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as
exports.NAME = ...
ormodule.exports = { ... }
. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the fileexport let foo, bar
from ESM to CommonJS, esbuild appends this to the end of the file:However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:
Basic support for index source maps (#3439, #4109)
The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.
This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.
Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.
This feature was contributed by @clyfish.
v0.25.1
Compare Source
Fix incorrect paths in inline source maps (#4070, #4075, #4105)
This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline
sourceMappingURL
data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing thesourceMappingURL
comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.Fix invalid generated source maps (#4080, #4082, #4104, #4107)
This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.
This fix was contributed by @jridgewell.
Fix a regression with non-file source map paths (#4078)
The format of paths in source maps that aren't in the
file
namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths fromfile
paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a:
character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.Fix a crash with
switch
optimization (#4088)The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:
Update Go from 1.23.5 to 1.23.7 (#4076, #4077)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.
This PR was contributed by @MikeWillCook.
parcel-bundler/lightningcss (lightningcss)
v1.29.3
Compare Source
::details-content
and::target-text
selectors – @philipp-spiess in https://github.com/parcel-bundler/lightningcss/pull/930:placeholder-shown
selector name across browsers – @Marukome0743 in https://github.com/parcel-bundler/lightningcss/pull/929/* cssmodules-pure-no-check */
comments – @jantimon in https://github.com/parcel-bundler/lightningcss/pull/898c03a7e7
v1.29.2
Compare Source
Browsers::load_browserslist
by @CPunisher in https://github.com/parcel-bundler/lightningcss/pull/8952284653
broofa/mime (mime)
v4.0.7
Compare Source
Bug Fixes
stackblitz-labs/pkg.pr.new (pkg-pr-new)
v0.0.42
Compare Source
v0.0.41
Compare Source
publint/publint (publint)
v0.3.11
Compare Source
Patch Changes
Update
EXPORTS_GLOB_NO_DEPRECATED_SUBPATH_MAPPING
message and severity to error (#179)Add a new warning when the
"exports"
or"imports"
field contain a fallback array as most tooling will only the pick the first value that can be parsed, and other tooling may work differently leading to inconsistent behaviors (#180)v0.3.10
Compare Source
Patch Changes
Support custom conditions in
"exports"
that points to raw TS or TSX files. This configuration is common in monorepo setups where packages refer to the raw files among themselves using a custom condition so custom aliasing isn't needed. (b34ea94
)With this support, the
"types"
condition is allowed to come after any exports of the raw TS or TSX files. File existence checks are also disabled for raw TS and TSX files reference as after publish these files may intentionally be not published.v0.3.9
Compare Source
Patch Changes
Support the
formatMessage
utility in the browser. It has a newcolor: 'html'
option to highlight important parts with<strong>
tags instead of ANSI colors. It also has a newreference: boolean
option so the messages are worded in reference of the message location. (e1cfef0
)If
formatMessage
is passed apackage.json
object with missing keys, the message part that references the value will now fallback to"undefined"
instead of completely erroring out. (45962d1
)typedoc2md/typedoc-plugin-markdown (typedoc-plugin-markdown)
v4.2.10
Compare Source
Patch Changes
v4.2.9
Compare Source
Patch Changes
@return
block tags on declarations (#694)v4.2.8
Compare Source
Patch Changes
v4.2.7
Compare Source
Patch Changes
v4.2.6
Compare Source
Patch Changes
v4.2.5
Compare Source
Patch Changes
<thead>
and<tbody>
elements to fix MDX compatibility issues (#671)v4.2.4
Compare Source
Patch Changes
v4.2.3
Compare Source
Patch Changes
v4.2.2
Compare Source
Patch Changes
v4.2.1
Compare Source
Patch Changes
felipecrs/typedoc-plugin-rename-defaults (typedoc-plugin-rename-defaults)
v0.7.3
Compare Source
v0.7.2
Compare Source
v0.7.1
Compare Source
Configuration
📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.