chore(deps): update npm packages #255
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/npm-packages
branch
from
29654b0
to
d1c8516
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-packages
branch
8 times, most recently
from
e0b5d28
to
f66c2ee
Compare
renovate
bot
force-pushed
the
renovate/npm-packages
branch
2 times, most recently
from
e32c092
to
1f13fdc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-packages
branch
2 times, most recently
from
374b4b7
to
2a5e8ad
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-packages
branch
2 times, most recently
from
40c156f
to
5fd1a77
Compare
renovate
bot
force-pushed
the
renovate/npm-packages
branch
from
5fd1a77
to
5f91ada
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:
19.3.0->19.4.03.7.1->3.8.04.19.2->4.20.020.14.11->20.14.157.16.1->7.18.07.16.1->7.18.09.7.0->9.9.07.34.4->7.35.09.1.1->9.1.415.2.7->15.2.85.5.3->5.5.4Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v19.4.0Compare Source
Features
lerna-lite/lerna-lite (@lerna-lite/cli)
v3.8.0Compare Source
Features
Bug Fixes
ionic-team/stencil (@stencil/core)
v4.20.0Compare Source
Bug Fixes
Note
As we’ve made further enhancements to support declarative Shadow DOM, the Stencil team has determined that it’s not feasible to allow users to render a shadow component as a scoped component after compilation, such as by calling
renderToStringwithserializeShadowRoot: false. This is because Stencil compiles styles for either shadow or scoped mode during the compilation process, embedding these styles into the hydrate module. Once this compilation is complete, the styles cannot be transformed to support the other mode. Recognizing that this change would impact the current functionality, the Stencil team has decided to proceed with this update. Moving forward, we recommend serializing all components marked with shadow: true as declarative Shadow DOM.typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.18.0Compare Source
🩹 Fixes
eslint-plugin: [no-unnecessary-type-assertion] prevent runtime error when asserting a variable declared in default TS lib
eslint-plugin: [unbound-method] report on destructuring in function parameters
eslint-plugin: [no-duplicate-type-constituents] shouldn't report on error types
eslint-plugin: [strict-boolean-expressions] support branded booleans
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.17.0Compare Source
🚀 Features
eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7
eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never"
🩹 Fixes
eslint-plugin: [no-floating-promises] check top-level type assertions (and more)
eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context
eslint-plugin: [no-unnecessary-condition] false positive on optional private field
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.18.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.17.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
eslint/eslint (eslint)
v9.9.0Compare Source
Features
41d0206feat: Add support for TS config files (#18134) (Arya Emami)3a4eaf9feat: add suggestion torequire-awaitto removeasynckeyword (#18716) (Dave)Documentation
9fe068cdocs: how to author plugins with configs that extend other configs (#18753) (Alec Gibson)48117b2docs: add version support page in the side navbar (#18738) (Amaresh S M)fec2951docs: add version support page to the dropdown (#18730) (Amaresh S M)38a0661docs: Fix typo (#18735) (Zaina Al Habash)3c32a9edocs: Update yarn command for creating ESLint config (#18739) (Temitope Ogunleye)f9ac978docs: Update README (GitHub Actions Bot)Chores
461b2c3chore: upgrade to@eslint/[email protected](#18765) (Francesco Trotta)59dba1bchore: package.json update for @eslint/js release (Jenkins)fea8563chore: update dependency @eslint/core to ^0.3.0 (#18724) (renovate[bot])aac191echore: update dependency @eslint/json to ^0.3.0 (#18760) (renovate[bot])b97fa05chore: update wdio dependencies for more stable tests (#18759) (Christian Bromann)v9.8.0Compare Source
jsx-eslint/eslint-plugin-react (eslint-plugin-react)
v7.35.0Compare Source
Added
jsx-props-no-spread-multi] (#3724 @SimonSchick)forbid-component-props]: addpropNamePatternto allow / disallow prop name patterns (#3774 @akulsr0)jsx-handler-names]: support ignoring component names (#3772 @akulsr0)jsx-closing-tag-location]: addline-alignedoption (#3777 @kimtaejin3)no-danger]: addcustomComponentNamesoption (#3748 @akulsr0)Fixed
no-invalid-html-attribute]: substitute placeholders in suggestion messages (#3759 @mdjermanovic)sort-prop-types]: single line type ending without semicolon (#3784 @akulsr0)require-default-props]: report when required props have default value (#3785 @akulsr0)Changed
variableUtil: Avoid creating a single flat variable scope for each lookup (#3782 @DanielRosenwasser)typicode/husky (husky)
v9.1.4Compare Source
v9.1.3Compare Source
PATHv9.1.2Compare Source
lint-staged/lint-staged (lint-staged)
v15.2.8Compare Source
Patch Changes
f0480f0Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version switched the--show-toplevelflag with--show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
Microsoft/TypeScript (typescript)
v5.5.4Compare Source
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.