Update devDependencies (major) (major) #35
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}
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:
^23.0.2->^24.0.0^2.2.0->^3.0.00.14.0->11.0.0^3.2.4->^4.0.0Release Notes
rollup/plugins
v24.0.0Compare Source
2022-12-18
Breaking Changes
vitejs/vite-plugin-react
v3.0.0Compare Source
rome/tools
v11.0.0CLI
BREAKING CHANGES
--no-colorshas been removed, in favor of--color=offOther changes
initcommand now adds the$schemaproperty to the generatedrome.jsonfileif
romeis installed inside thenode_modulesfolder. Follow this guide to add the$schemapropertymanually in a project with an existing
rome.jsonfile.--semicolonsoption that configures if the formatter prints semicolons at the end of every statement (default) or at the beginning of statements when necessary to prevent ASI failures.Rome now prints the total number of errors caused in the files.
--colorsoption with the valueforce. Forcing color output can be useful if you spawn Rome as a subprocess.Rome is spawned as a process;
Configuration
$schemaproperty. The schema enables auto-completion by editors and...auto-completion and descriptions of all fields of the configuration file.
files.ignoreoption where users can ignore files across tools.Editors
node_modulesfolder.Formatter
BREAKING CHANGES
jestEachtemplatesOther changes
Linter
noUselessFragments#3668noArrayIndexKeywhere some cases were not detected #3670noConstAssign#3728noShoutyConstants#3867noUnusedVariables#3779noUndeclaredVariableswhere some cases were not detected #3798noUndeclaredVariableswhere types were incorrectly detected #3669Rules
The following rules have been stabilized:
nursery/useFlatMap->complexity/useFlatMapnursery/useValidForDirection->correctness/useValidForDirectionnursery/noExplicitAny->suspicious/noExplicitAnynursery/noConstAssign->correctness/noConstAssignThese rules are all recommended, so they will be enabled by default. You can simply remove those entries from your configuration file if you had enabled them manually from the
nurserygroup.The following rules have been renamed:
a11y/useBlankTarget->a11y/noBlankTargetcorrectness/noMultipleSpacesInRegularExpressionLiterals->complexity/noMultipleSpacesInRegularExpressionLiteralsstyle/useOptionalChain->complexity/useOptionalChaincorrectness/noUselessFragments->complexity/noUselessFragmentscorrectness/noDelete->performance/noDeletecorrectness/useSingleCaseStatement->style/useSingleCaseStatementcorrectness/useWhile->style/useWhilecorrectness/noArguments->style/noArgumentscorrectness/noAsyncPromiseExecutor->suspicious/noAsyncPromiseExecutorcorrectness/noCommentText->suspicious/noCommentTextcorrectness/noCompareNegZero->suspicious/noCompareNegZerocorrectness/noDebugger->suspicious/noDebuggercorrectness/noDoubleEquals->suspicious/noDoubleEqualscorrectness/noShadowRestrictedNames->suspicious/noShadowRestrictedNamescorrectness/noSparseArray->suspicious/noSparseArraycorrectness/noUnsafeNegation->suspicious/noUnsafeNegationcorrectness/useValidTypeof->suspicious/useValidTypeofcorrectness/noArrayIndexKey->suspicious/noArrayIndexKeycorrectness/noCatchAssign->suspicious/noCatchAssigncorrectness/noDupeArgs->suspicious/noDuplicateParameterscorrectness/noFunctionAssign->suspicious/noFunctionAssigncorrectness/noImportAssign->suspicious/noImportAssigncorrectness/noLabelVar->suspicious/noLabelVarcorrectness/noRestrictedGlobals->nursery/noRestrictedGlobalsnursery/noDupeKeys->nursery/noDuplicateObjectKeysIf you were not changing the severity level of any of these rules in your configuration file, or suppressing a diagnostic emitted by those rules using suppression comments, you do not have to do anything. But if you did, Rome will now emit diagnostics for the parts of your configuration or suppression comments you need to update.
The following rules are no longer recommended:
style/noImplicitBooleanstyle/noNegationElsestyle/useBlockStatementsstyle/useShorthandArrayTypecorrectness/useSingleCaseStatement/style/useSingleCaseStatementstyle/noShoutyConstantsThe styling decisions imposed by these rules were not deemed to be idiomatic enough in the JavaScript ecosystem to be enabled by default. If you do want to enforce those rules in your project, you will have to enable them manually in you configuration file:
{ "linter": { "rules": { "style": { "useBlockStatements": "warn" } } } }Finally, the following new rules have been introduced to the nursery group in this release:
nursery/noAccessKeynursery/noConditionalAssignmentnursery/noConstEnumnursery/noConstructorReturnnursery/noDistractingElementsnursery/noDuplicateObjectKeysnursery/noEmptyInterfacenursery/noExtraNonNullAssertionnursery/noHeaderScopenursery/noNonNullAssertionnursery/noPrecisionLossnursery/noRedundantUseStrictnursery/noSetterReturnnursery/noStringCaseMismatchnursery/noUnsafeFinallynursery/noVoidTypeReturnnursery/useDefaultSwitchClauseLastnursery/useNumericLiteralsnursery/useAriaPropTypesnursery/useAriaPropsForRolenursery/noVarnursery/useConstPlease give them a try by manually enabling them in your configuration and please share your feedback on the rule, diagnostics, and code fixes.
Parser
JSON;satisfieskeyword;asyncused as label #3612export default functionind.tsfiles #3485awaitin non-async contexts #2479VSCode
JavaScript APIs
Breaking change
backendhas been removed, in favor of the concept ofdistribution.Other changes
v10.0.1CLI
enabledflag from configuration (#3591)Formatter
Linter
noUselessFragments,noArrayIndexKey,noChildrenProp,noUselessFragments,noVoidElementsWithChildren,noDangerouslySetInnerHtml,noDangerouslySetInnerHtmlWithChildren,useValidAnchor,noRenderReturnValue,noUnusedVariablesanduseKeyWithClickEvents(#3592, #3619, #3599, #3626, #3620 & #3644)
Editors
v10.0.0CLI
rome version.rome rage.rome lsp-proxy.--versionas an alias forrome version--files-max-sizeto change the allowed size of files, in bytes.--formatter-enabledto the commandrome ci.--linter-enabledto the commandrome ci.formatoption--trailing-commato configure where to add trailing commas.rome ci, closes #3456.rome cicommand to run the linter even if the formatter is disabled, closes #3495.Configuration
files.maxSize, to change the allowed size of files, in bytes.Diagnostics
Formatter
all,es5andnone; refer to the documentation to learn more.Linter
noUnreachablerulenoNegationElse#3141noUnusedVariables#3169New rules
noAutoFocususeAltTextnoBlankTargetuseAnchorContentuseKeyWithClickEventsuseKeyWithMouseEventsnoPositiveTabIndexuseValidAnchornoRestrictedGlobalsuseSimplifiedBooleanExpressionnoInvalidConstructorSuperuseValidForDirectionnoConstAssignnoExplicitAnynoBannedTypesuseMapFlatuseExhaustiveDependenciesParser
export {"a"} from "b";wasn't correctly parsedVSCode
Restart LSP Serverrome.jsonand apply the new configurationv3.0.0Compare Source
v2.1.22Compare Source
v2.1.21Compare Source
v2.1.20Compare Source
v2.1.19Compare Source
v2.1.17Compare Source
v2.1.16Compare Source
v2.1.15Compare Source
v2.1.14Compare Source
v2.1.13Compare Source
v2.1.12Compare Source
v2.1.11Compare Source
v2.1.10Compare Source
v2.1.9Compare Source
v2.1.8Compare Source
v2.1.7Compare Source
v2.1.5Compare Source
v2.1.4Compare Source
v2.1.3Compare Source
v2.1.2Compare Source
v2.1.1Compare Source
v2.1.0Compare Source
v2.0.4Compare Source
v2.0.3Compare Source
v2.0.2Compare Source
v2.0.1Compare Source
v2.0.0Compare Source
v1.2.4Compare Source
v1.2.3Compare Source
v1.2.2Compare Source
v1.2.1Compare Source
v1.2.0Compare Source
v1.1.6Compare Source
v1.1.5Compare Source
v1.1.4Compare Source
v1.1.3Compare Source
v1.1.2Compare Source
v1.1.1Compare Source
v1.1.0Compare Source
v1.0.3Compare Source
v1.0.2Compare Source
v1.0.1Compare Source
v1.0.0Compare Source
CLI
BREAKING CHANGES
--no-colorshas been removed, in favor of--color=offOther changes
initcommand now adds the$schemaproperty to the generatedrome.jsonfileif
romeis installed inside thenode_modulesfolder. Follow this guide to add the$schemapropertymanually in a project with an existing
rome.jsonfile.--semicolonsoption that configures if the formatter prints semicolons at the end of every statement (default) or at the beginning of statements when necessary to prevent ASI failures.Rome now prints the total number of errors caused in the files.
--colorsoption with the valueforce. Forcing color output can be useful if you spawn Rome as a subprocess.Rome is spawned as a process;
Configuration
$schemaproperty. The schema enables auto-completion by editors and...auto-completion and descriptions of all fields of the configuration file.
files.ignoreoption where users can ignore files across tools.Editors
node_modulesfolder.Formatter
BREAKING CHANGES
jestEachtemplatesOther changes
Linter
noUselessFragments#3668noArrayIndexKeywhere some cases were not detected #3670noConstAssign#3728noShoutyConstants#3867noUnusedVariables#3779noUndeclaredVariableswhere some cases were not detected #3798noUndeclaredVariableswhere types were incorrectly detected #3669Rules
The following rules have been stabilized:
nursery/useFlatMap->complexity/useFlatMapnursery/useValidForDirection->correctness/useValidForDirectionnursery/noExplicitAny->suspicious/noExplicitAnynursery/noConstAssign->correctness/noConstAssignThese rules are all recommended, so they will be enabled by default. You can simply remove those entries from your configuration file if you had enabled them manually from the
nurserygroup.The following rules have been renamed:
a11y/useBlankTarget->a11y/noBlankTargetcorrectness/noMultipleSpacesInRegularExpressionLiterals->complexity/noMultipleSpacesInRegularExpressionLiteralsstyle/useOptionalChain->complexity/useOptionalChaincorrectness/noUselessFragments->complexity/noUselessFragmentscorrectness/noDelete->performance/noDeletecorrectness/useSingleCaseStatement->style/useSingleCaseStatementcorrectness/useWhile->style/useWhilecorrectness/noArguments->style/noArgumentscorrectness/noAsyncPromiseExecutor->suspicious/noAsyncPromiseExecutorcorrectness/noCommentText->suspicious/noCommentTextcorrectness/noCompareNegZero->suspicious/noCompareNegZerocorrectness/noDebugger->suspicious/noDebuggercorrectness/noDoubleEquals->suspicious/noDoubleEqualscorrectness/noShadowRestrictedNames->suspicious/noShadowRestrictedNamescorrectness/noSparseArray->suspicious/noSparseArraycorrectness/noUnsafeNegation->suspicious/noUnsafeNegationcorrectness/useValidTypeof->suspicious/useValidTypeofcorrectness/noArrayIndexKey->suspicious/noArrayIndexKeycorrectness/noCatchAssign->suspicious/noCatchAssigncorrectness/noDupeArgs->suspicious/noDuplicateParameterscorrectness/noFunctionAssign->suspicious/noFunctionAssigncorrectness/noImportAssign->suspicious/noImportAssigncorrectness/noLabelVar->suspicious/noLabelVarcorrectness/noRestrictedGlobals->nursery/noRestrictedGlobalsnursery/noDupeKeys->nursery/noDuplicateObjectKeysIf you were not changing the severity level of any of these rules in your configuration file, or suppressing a diagnostic emitted by those rules using suppression comments, you do not have to do anything. But if you did, Rome will now emit diagnostics for the parts of your configuration or suppression comments you need to update.
The following rules are no longer recommended:
style/noImplicitBooleanstyle/noNegationElsestyle/useBlockStatementsstyle/useShorthandArrayTypecorrectness/useSingleCaseStatement/style/useSingleCaseStatementstyle/noShoutyConstantsThe styling decisions imposed by these rules were not deemed to be idiomatic enough in the JavaScript ecosystem to be enabled by default. If you do want to enforce those rules in your project, you will have to enable them manually in you configuration file:
{ "linter": { "rules": { "style": { "useBlockStatements": "warn" } } } }Finally, the following new rules have been introduced to the nursery group in this release:
nursery/noAccessKeynursery/noConditionalAssignmentnursery/noConstEnumnursery/noConstructorReturnnursery/noDistractingElementsnursery/noDuplicateObjectKeysnursery/noEmptyInterfacenursery/noExtraNonNullAssertionnursery/noHeaderScopenursery/noNonNullAssertionnursery/noPrecisionLossnursery/noRedundantUseStrictnursery/noSetterReturnnursery/noStringCaseMismatchnursery/noUnsafeFinallynursery/noVoidTypeReturnnursery/useDefaultSwitchClauseLastnursery/useNumericLiteralsnursery/useAriaPropTypesnursery/useAriaPropsForRolenursery/noVarnursery/useConstPlease give them a try by manually enabling them in your configuration and please share your feedback on the rule, diagnostics, and code fixes.
Parser
JSON;satisfieskeyword;asyncused as label #3612export default functionind.tsfiles #3485awaitin non-async contexts #2479VSCode
JavaScript APIs
Breaking change
backendhas been removed, in favor of the concept ofdistribution.Other changes
vitejs/vite
v4.0.3Compare Source
v4.0.2Compare Source
toOutputFilePathWithoutRuntimefunction (#11367) (8820f75), closes #11367vite optimizeprebundle for dev (#11387) (b4ced0f), closes #11387v4.0.1Compare Source
u(#11319) (8c0bb7b), closes #11319useDefineForClassFieldsvalue fromtsconfig.compilerOptions.target(fixes #10296) (# (42976d8), closes #10296 #11301/__open-in-editor(#11337) (8856c2e), closes #11337@typescript-eslint/ban-ts-comment(#11326) (e58a4f0), closes #11326v4.0.0Compare Source
Read the announcement blog post: Announcing Vite 4
Quick links:
Docs in other languages:
Main Changes
This major is smaller in scope compared to Vite 3, with the main objective of upgrading to Rollup 3. We've worked with the ecosystem to ensure a smooth upgrade path for this new major.
Rollup 3
Vite is now using Rollup 3, which allowed us to simplify Vite's internal asset handling and has many improvements. See the Rollup 3 release notes here.
Framework Plugins out of the Vite core monorepo
@vitejs/plugin-vueand@vitejs/plugin-reacthave been part of Vite core monorepo since the first versions of Vite. This helped us to get a close feedback loop when making changes as we were getting both Core and the plugins tested and released together. With vite-ecosystem-ci we can get this feedback with these plugins developed on independent repositories, so from Vite 4, they have been moved out of the Vite core monorepo. This is meaningful for Vite's framework-agnostic story, and will allow us to build independent teams to maintain each of the plugins. If you have bugs to report or features to request, please create issues on the new repositories moving forward:vitejs/vite-plugin-vueandvitejs/vite-plugin-react.New React plugin using SWC during development
SWC is now a mature replacement for Babel, especially in the context of React projects. SWC's React Fast Refresh implementation is a lot faster than Babel, and for some projects, it is now a better alternative. From Vite 4, two plugins are available for React projects with different tradeoffs. We believe that both approaches are worth supporting at this point, and we'll continue to explore improvements to both plugins in the future.
@vitejs/plugin-react
@vitejs/plugin-react is a plugin that uses esbuild and Babel, achieving fast HMR with a small package footprint and the flexibility of being able to use the babel transform pipeline.
@vitejs/plugin-react-swc (new)
@vitejs/plugin-react-swc is a new plugin that uses esbuild during build, but replaces Babel with SWC during development. For big projects that don't require non-standard React extensions, cold start and Hot Module Replacement (HMR) can be significantly faster.
Compatibility
The modern browser build now targets
safari14by default for wider ES2020 compatibility (https://github.com/vitejs/vite/issues/9063). This means that modern builds can now useBigIntand that the nullish coallessing operator isn't transpiled anymore. If you need to support older browsers, you can add@vitejs/plugin-legacyas usual.Importing CSS as a string
In Vite 3, importing the default export of a
.cssfile could introduce a double loading of CSS.This double loading could occur since a
.cssfile will be emitted and it's likely that the CSS string will also be used by the application code — for example, injected by the framework runtime. From Vite 4, the.cssdefault export has been deprecated. The?inlinequery suffix modifier needs to be used in this case, as that doesn't emit the imported.cssstyles.Other features
kBto align with browser dev tools (#10982)Features
expand(#11141) (825c793), closes #11141safari14by default for wider ES2020 compatibility (#9063) (3cc65d7), closes #9063Configuration
📅 Schedule: Branch creation - "every weekend" (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.