chore(deps): update dependency rome to v11 - autoclosed #403
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:
0.10.0-next
->11.0.0
Release Notes
rome/tools
v11.0.0
CLI
BREAKING CHANGES
--no-colors
has been removed, in favor of--color=off
Other changes
init
command now adds the$schema
property to the generatedrome.json
fileif
rome
is installed inside thenode_modules
folder. Follow this guide to add the$schema
propertymanually in a project with an existing
rome.json
file.--semicolons
option 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.
--colors
option with the valueforce
. Forcing color output can be useful if you spawn Rome as a subprocess.Rome is spawned as a process;
Configuration
$schema
property. The schema enables auto-completion by editors and...auto-completion and descriptions of all fields of the configuration file.
files.ignore
option where users can ignore files across tools.Editors
node_modules
folder.Formatter
BREAKING CHANGES
jestEach
templatesOther changes
Linter
noUselessFragments
#3668noArrayIndexKey
where some cases were not detected #3670noConstAssign
#3728noShoutyConstants
#3867noUnusedVariables
#3779noUndeclaredVariables
where some cases were not detected #3798noUndeclaredVariables
where types were incorrectly detected #3669Rules
The following rules have been stabilized:
nursery/useFlatMap
->complexity/useFlatMap
nursery/useValidForDirection
->correctness/useValidForDirection
nursery/noExplicitAny
->suspicious/noExplicitAny
nursery/noConstAssign
->correctness/noConstAssign
These 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
nursery
group.The following rules have been renamed:
a11y/useBlankTarget
->a11y/noBlankTarget
correctness/noMultipleSpacesInRegularExpressionLiterals
->complexity/noMultipleSpacesInRegularExpressionLiterals
style/useOptionalChain
->complexity/useOptionalChain
correctness/noUselessFragments
->complexity/noUselessFragments
correctness/noDelete
->performance/noDelete
correctness/useSingleCaseStatement
->style/useSingleCaseStatement
correctness/useWhile
->style/useWhile
correctness/noArguments
->style/noArguments
correctness/noAsyncPromiseExecutor
->suspicious/noAsyncPromiseExecutor
correctness/noCommentText
->suspicious/noCommentText
correctness/noCompareNegZero
->suspicious/noCompareNegZero
correctness/noDebugger
->suspicious/noDebugger
correctness/noDoubleEquals
->suspicious/noDoubleEquals
correctness/noShadowRestrictedNames
->suspicious/noShadowRestrictedNames
correctness/noSparseArray
->suspicious/noSparseArray
correctness/noUnsafeNegation
->suspicious/noUnsafeNegation
correctness/useValidTypeof
->suspicious/useValidTypeof
correctness/noArrayIndexKey
->suspicious/noArrayIndexKey
correctness/noCatchAssign
->suspicious/noCatchAssign
correctness/noDupeArgs
->suspicious/noDuplicateParameters
correctness/noFunctionAssign
->suspicious/noFunctionAssign
correctness/noImportAssign
->suspicious/noImportAssign
correctness/noLabelVar
->suspicious/noLabelVar
correctness/noRestrictedGlobals
->nursery/noRestrictedGlobals
nursery/noDupeKeys
->nursery/noDuplicateObjectKeys
If 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/noImplicitBoolean
style/noNegationElse
style/useBlockStatements
style/useShorthandArrayType
correctness/useSingleCaseStatement
/style/useSingleCaseStatement
style/noShoutyConstants
The 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:
Finally, the following new rules have been introduced to the nursery group in this release:
nursery/noAccessKey
nursery/noConditionalAssignment
nursery/noConstEnum
nursery/noConstructorReturn
nursery/noDistractingElements
nursery/noDuplicateObjectKeys
nursery/noEmptyInterface
nursery/noExtraNonNullAssertion
nursery/noHeaderScope
nursery/noNonNullAssertion
nursery/noPrecisionLoss
nursery/noRedundantUseStrict
nursery/noSetterReturn
nursery/noStringCaseMismatch
nursery/noUnsafeFinally
nursery/noVoidTypeReturn
nursery/useDefaultSwitchClauseLast
nursery/useNumericLiterals
nursery/useAriaPropTypes
nursery/useAriaPropsForRole
nursery/noVar
nursery/useConst
Please 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
;satisfies
keyword;async
used as label #3612export default function
ind.ts
files #3485await
in non-async contexts #2479VSCode
JavaScript APIs
Breaking change
backend
has been removed, in favor of the concept ofdistribution
.Other changes
v10.0.1
CLI
enabled
flag from configuration (#3591)Formatter
Linter
noUselessFragments
,noArrayIndexKey
,noChildrenProp
,noUselessFragments
,noVoidElementsWithChildren
,noDangerouslySetInnerHtml
,noDangerouslySetInnerHtmlWithChildren
,useValidAnchor
,noRenderReturnValue
,noUnusedVariables
anduseKeyWithClickEvents
(#3592, #3619, #3599, #3626, #3620 & #3644)
Editors
v10.0.0
CLI
rome version
.rome rage
.rome lsp-proxy
.--version
as an alias forrome version
--files-max-size
to change the allowed size of files, in bytes.--formatter-enabled
to the commandrome ci
.--linter-enabled
to the commandrome ci
.format
option--trailing-comma
to configure where to add trailing commas.rome ci
, closes #3456.rome ci
command 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
,es5
andnone
; refer to the documentation to learn more.Linter
noUnreachable
rulenoNegationElse
#3141noUnusedVariables
#3169New rules
noAutoFocus
useAltText
noBlankTarget
useAnchorContent
useKeyWithClickEvents
useKeyWithMouseEvents
noPositiveTabIndex
useValidAnchor
noRestrictedGlobals
useSimplifiedBooleanExpression
noInvalidConstructorSuper
useValidForDirection
noConstAssign
noExplicitAny
noBannedTypes
useMapFlat
useExhaustiveDependencies
Parser
export {"a"} from "b";
wasn't correctly parsedVSCode
Restart LSP Server
rome.json
and apply the new configurationv3.0.0
Compare Source
v2.1.22
Compare Source
v2.1.21
Compare Source
v2.1.20
Compare Source
v2.1.19
Compare Source
v2.1.17
Compare Source
v2.1.16
Compare Source
v2.1.15
Compare Source
v2.1.14
Compare Source
v2.1.13
Compare Source
v2.1.12
Compare Source
v2.1.11
Compare Source
v2.1.10
Compare Source
v2.1.9
Compare Source
v2.1.8
Compare Source
v2.1.7
Compare Source
v2.1.5
Compare Source
v2.1.4
Compare Source
v2.1.3
Compare Source
v2.1.2
Compare Source
v2.1.1
Compare Source
v2.1.0
Compare Source
v2.0.4
Compare Source
v2.0.3
Compare Source
v2.0.2
Compare Source
v2.0.1
Compare Source
v2.0.0
Compare Source
v1.2.4
Compare Source
v1.2.3
Compare Source
v1.2.2
Compare Source
v1.2.1
Compare Source
v1.2.0
Compare Source
v1.1.6
Compare Source
v1.1.5
Compare Source
v1.1.4
Compare Source
v1.1.3
Compare Source
v1.1.2
Compare Source
v1.1.1
Compare Source
v1.1.0
Compare Source
v1.0.3
Compare Source
v1.0.2
Compare Source
v1.0.1
Compare Source
v1.0.0
Compare Source
CLI
BREAKING CHANGES
--no-colors
has been removed, in favor of--color=off
Other changes
init
command now adds the$schema
property to the generatedrome.json
fileif
rome
is installed inside thenode_modules
folder. Follow this guide to add the$schema
propertymanually in a project with an existing
rome.json
file.--semicolons
option 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.
--colors
option with the valueforce
. Forcing color output can be useful if you spawn Rome as a subprocess.Rome is spawned as a process;
Configuration
$schema
property. The schema enables auto-completion by editors and...auto-completion and descriptions of all fields of the configuration file.
files.ignore
option where users can ignore files across tools.Editors
node_modules
folder.Formatter
BREAKING CHANGES
jestEach
templatesOther changes
Linter
noUselessFragments
#3668noArrayIndexKey
where some cases were not detected #3670noConstAssign
#3728noShoutyConstants
#3867noUnusedVariables
#3779noUndeclaredVariables
where some cases were not detected #3798noUndeclaredVariables
where types were incorrectly detected #3669Rules
The following rules have been stabilized:
nursery/useFlatMap
->complexity/useFlatMap
nursery/useValidForDirection
->correctness/useValidForDirection
nursery/noExplicitAny
->suspicious/noExplicitAny
nursery/noConstAssign
->correctness/noConstAssign
These 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
nursery
group.The following rules have been renamed:
a11y/useBlankTarget
->a11y/noBlankTarget
correctness/noMultipleSpacesInRegularExpressionLiterals
->complexity/noMultipleSpacesInRegularExpressionLiterals
style/useOptionalChain
->complexity/useOptionalChain
correctness/noUselessFragments
->complexity/noUselessFragments
correctness/noDelete
->performance/noDelete
correctness/useSingleCaseStatement
->style/useSingleCaseStatement
correctness/useWhile
->style/useWhile
correctness/noArguments
->style/noArguments
correctness/noAsyncPromiseExecutor
->suspicious/noAsyncPromiseExecutor
correctness/noCommentText
->suspicious/noCommentText
correctness/noCompareNegZero
->suspicious/noCompareNegZero
correctness/noDebugger
->suspicious/noDebugger
correctness/noDoubleEquals
->suspicious/noDoubleEquals
correctness/noShadowRestrictedNames
->suspicious/noShadowRestrictedNames
correctness/noSparseArray
->suspicious/noSparseArray
correctness/noUnsafeNegation
->suspicious/noUnsafeNegation
correctness/useValidTypeof
->suspicious/useValidTypeof
correctness/noArrayIndexKey
->suspicious/noArrayIndexKey
correctness/noCatchAssign
->suspicious/noCatchAssign
correctness/noDupeArgs
->suspicious/noDuplicateParameters
correctness/noFunctionAssign
->suspicious/noFunctionAssign
correctness/noImportAssign
->suspicious/noImportAssign
correctness/noLabelVar
->suspicious/noLabelVar
correctness/noRestrictedGlobals
->nursery/noRestrictedGlobals
nursery/noDupeKeys
->nursery/noDuplicateObjectKeys
If 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/noImplicitBoolean
style/noNegationElse
style/useBlockStatements
style/useShorthandArrayType
correctness/useSingleCaseStatement
/style/useSingleCaseStatement
style/noShoutyConstants
The 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:
Finally, the following new rules have been introduced to the nursery group in this release:
nursery/noAccessKey
nursery/noConditionalAssignment
nursery/noConstEnum
nursery/noConstructorReturn
nursery/noDistractingElements
nursery/noDuplicateObjectKeys
nursery/noEmptyInterface
nursery/noExtraNonNullAssertion
nursery/noHeaderScope
nursery/noNonNullAssertion
nursery/noPrecisionLoss
nursery/noRedundantUseStrict
nursery/noSetterReturn
nursery/noStringCaseMismatch
nursery/noUnsafeFinally
nursery/noVoidTypeReturn
nursery/useDefaultSwitchClauseLast
nursery/useNumericLiterals
nursery/useAriaPropTypes
nursery/useAriaPropsForRole
nursery/noVar
nursery/useConst
Please 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
;satisfies
keyword;async
used as label #3612export default function
ind.ts
files #3485await
in non-async contexts #2479VSCode
JavaScript APIs
Breaking change
backend
has been removed, in favor of the concept ofdistribution
.Other changes
v0.14.0
Compare Source
v0.13.0
Compare Source
v0.12.1
Compare Source
v0.12.0
Compare Source
v0.11.2
Compare Source
v0.11.1
Compare Source
v0.10.1
CLI
Diagnostics
VSCode
v0.10.0
Core
Configuration
You can now ignore folders and files using the Unix shell style patterns:
Formatter
Linter
were named after a language, and this caused confusion among users and contributors. Please
check our website to know better about the new groups.
The new groups are heavily inspired from
clippy
nursery
, this group incubates new rules that are being developed.style
, this group incubates rules that orbits around styling.correctness
, this group incubates rules that orbits catching possible bugs.useBlockStatements
#3199useCamelCase
#3190 #3210useOptionalChain
#3257noUnusedVariables
#3170, #3316New rules
useButtonType
noRenderReturnValue
noDangerouslySetInnerHtml
useOptionalChain
useFragmentSyntax
noUselessFragments
noChildrenProp
noArrayIndexKey
noVoidElementsWithChildren
noUndeclaredVariables
noDangerouslySetInnerHtmlWithChildren
Parser
VSCode
lspBin
can be also expressed as relative pathwhen editing the
rome.json
for therules
sectionConfiguration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.