fix(deps): update all non-major dependencies #22
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:
17.7.0
->17.8.0
2.0.0
->2.6.0
16.4.0
->16.5.2
5.0.0
->5.0.1
7.4.0
->7.4.6
7.4.0
->7.4.6
7.4.0
->7.4.6
7.4.0
->7.4.6
7.4.0
->7.4.6
7.4.0
->7.4.6
6.1.3
->6.1.4
29.2.3
->29.5.5
6.2.0
->6.7.5
6.6.0
->6.7.5
4.0.0
->4.1.0
0.19.0
->0.19.4
8.49.0
->8.51.0
17.0.0
->17.1.0
2.26.0
->2.28.1
10.3.7
->10.3.10
15.0.0
->15.0.1
3.0.0
->3.0.3
0.2.2
->0.2.4
7.4.0
->7.4.6
2.4.1
->2.6.2
7.1.0
->7.2.0
1.6.3
->1.10.15
4.4.5
->4.4.11
Release Notes
conventional-changelog/commitlint (@commitlint/config-conventional)
v17.8.0
Compare Source
Note: Version bump only for package @commitlint/config-conventional
lerna-lite/lerna-lite (@lerna-lite/cli)
v2.6.0
Compare Source
Features
--force-conventional-graduate
to force update (#743) (d9de881) - by @ghiscodingv2.5.1
Compare Source
Bug Fixes
v2.5.0
Compare Source
Note: Version bump only for package @lerna-lite/cli
v2.4.2
Compare Source
Bug Fixes
v2.4.1
Compare Source
Note: Version bump only for package @lerna-lite/cli
v2.4.0
Compare Source
Features
--create-release-discussion
option (#604) (c246d0d) - by @ghiscodingv2.3.0
Compare Source
Note: Version bump only for package @lerna-lite/cli
v2.2.0
Compare Source
Bug Fixes
v2.1.0
Compare Source
Bug Fixes
publish
module ifcli
inside a monorepo package (#573) (6cb85d8) - by @johnsoncodehkcli
inside a monorepo package (#578) (c1979dd) - by @ghiscodingrollup/plugins (@rollup/plugin-alias)
v5.0.1
Compare Source
2023-10-05
Bugfixes
storybookjs/storybook (@storybook/addon-actions)
v7.4.6
Compare Source
v7.4.5
Compare Source
v7.4.4
Compare Source
v7.4.3
Compare Source
v7.4.2
Compare Source
v7.4.1
Compare Source
sb add
- #24079, thanks @Integrayshaun!@types/react
dep from@storybook/types
- #24042, thanks @JReinhold!testing-library/jest-dom (@testing-library/jest-dom)
v6.1.4
Compare Source
Bug Fixes
@adobe/css-tools
to4.3.1
to address vulnerability (#532) (44f1eab)typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.7.5
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.7.4
Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.7.3
Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.7.2
Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.7.0
Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
v6.6.0
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.5.0
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
6.4.1 (2023-08-21)
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.4.1
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.4.0
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.3.0
Compare Source
Bug Fixes
allowTypeImports
enabled (#7379) (cc9a46d)Features
ignorePrimitives
option to betrue
(#7331) (dfcafae)Reverts
You can read about our versioning strategy and releases on our website.
6.2.1 (2023-07-31)
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.2.1
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.7.5
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.7.4
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.7.3
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.7.2
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.7.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.1.0
Compare Source
@types/babel__cores
to dependencies (fix #211)@babel/core
#212index.d.cts
file so you don't get types errors when settingmoduleResolution
tonode16
ornodenext
in your tsconfig (we recommend usingbundler
which is more close to how Vite works)v4.0.4
Compare Source
v4.0.3
Compare Source
v4.0.2
Compare Source
v4.0.1
Compare Source
evanw/esbuild (esbuild)
v0.19.4
Compare Source
Fix printing of JavaScript decorators in tricky cases (#3396)
This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:
Allow pre-release versions to be passed to
target
(#3388)People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's
target
setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed totarget
and do something reasonable with them.v0.19.3
Compare Source
Fix
list-style-type
with thelocal-css
loader (#3325)The
local-css
loader incorrectly treated all identifiers provided tolist-style-type
as a custom local identifier. That included identifiers such asnone
which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:Note that this bug only affected code using the
local-css
loader. It did not affect code using thecss
loader.Avoid inserting temporary variables before
use strict
(#3322)This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before
use strict
directives:Adjust TypeScript
enum
output to better approximatetsc
(#3329)TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:
However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:
The template literal initializer for
PRESENT
is treated as a string while the template literal initializer forMISSING
is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior oftsc
but in the case where the behavior divergestsc
reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see thedeclare
keyword), which esbuild deliberately doesn't do.Ignore case in CSS in more places (#3316)
This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:
Please never actually write code like this.
Improve the error message for
null
entries inexports
(#3377)Package authors can disable package export paths with the
exports
map inpackage.json
. With this release, esbuild now has a clearer error message that points to thenull
token inpackage.json
itself instead of to the surrounding context. Here is an example of the new error message:Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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.