chore(deps): update dependency rome to v11 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rome (source)	10.0.1 -> 11.0.0

---

Release Notes

rome/tools

v11.0.0

CLI

BREAKING CHANGES

• the argument --no-colors has been removed, in favor of --color=off

Other changes

• The init command now adds the $schema property to the generated rome.json file
  if rome is installed inside the node_modules folder. Follow this guide to add the $schema property
  manually in a project with an existing rome.json file.
• A new --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 exits with an error code if it doesn't process any file.
• Fixed how the maximum number of diagnostics is calculated #​3869.
  Rome now prints the total number of errors caused in the files.
• Rome now traverses symbolic links and emits warnings if it detects loops, and continues processing the next file during the directory traversal.
• You can force color output using the new global --colors option with the value force. Forcing color output can be useful if you spawn Rome as a subprocess.
  Rome is spawned as a process;

Configuration

• Added the JSON schema $schema property. The schema enables auto-completion by editors and...
  auto-completion and descriptions of all fields of the configuration file.
• Added a new files.ignore option where users can ignore files across tools.

Editors

• We also publish Rome to Open VSX.
• The extension now resolves the Rome version installed in the node_modules folder.
• Fixed an issue where diagnostics were not updated after a change to the configuration file (#​3724)[https://github.com/rome/tools/pull/3724](https://togithub.com/rome/tools/pull/3724)4]
• The LSP emits a new action where the user can suppress a rule.
• The extension now allows sort imports

Formatter

BREAKING CHANGES

• Fixed incompatibility issues with Prettier #​3531
  • #​3686
  • #​3732
  • #​3842
• Fixed an issue where infinite parentheses were wrongly inserted #​3735
• Better formatting for jestEach templates

Other changes

• Added support for omitting semicolons.

Linter

• Fixed false positives emitted by noUselessFragments #​3668
• Fixed noArrayIndexKey where some cases were not detected #​3670
• Fixed false positives emitted by noConstAssign #​3728
• Fixed false positives emitted by noShoutyConstants #​3867
• Fixed false positives emitted by noUnusedVariables #​3779
• Fixed noUndeclaredVariables where some cases were not detected #​3798
• Fixed noUndeclaredVariables where types were incorrectly detected #​3669

Rules

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:

{
  "linter": {
    "rules": {
        "style": {
            "useBlockStatements": "warn"
        }
    }
  }
}

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

• Added support for JSON;
• Added support satisfies keyword;
• Fixed parse for async used as label #​3612
• Fixed parse of export default function in d.ts files #​3485
• Improved the parsing of await in non-async contexts #​2479

VSCode

• Removed the "preview" label from the extension.
• Improved logging when the extension can't connect to the server. #​3920

JavaScript APIs

Breaking change

• The concept of backend has been removed, in favor of the concept of distribution.
• Removed the possibility to connect to the daemon, for the time being.
• The APIs are asynchronous anymore.

Other changes

• The package has been marked as unstable and in alpha state.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
moviesmap	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Mar 7, 2023 at 11:16AM (UTC)