Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 10, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rome (source) 0.10.0-next -> 11.0.0 age adoption passing confidence

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
Formatter
BREAKING CHANGES
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:

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.

v10.0.1

CLI
  • Respect the formatter / linter enabled flag from configuration (#​3591)
  • Correctly account for diff diagnostics in the printed diagnostics count (#​3595)
Formatter
  • Do not insert a trailing comma in import expressions (#​3600)
Linter
  • Fixed false positives in noUselessFragments, noArrayIndexKey, noChildrenProp, noUselessFragments, noVoidElementsWithChildren, noDangerouslySetInnerHtml, noDangerouslySetInnerHtmlWithChildren, useValidAnchor, noRenderReturnValue, noUnusedVariables and useKeyWithClickEvents
    (#​3592, #​3619, #​3599, #​3626, #​3620 & #​3644)
Editors
  • Display the version of the language server in the status bar (#​3616)

v10.0.0

CLI
  • Added the new command rome version.
  • Added the new command rome rage.
  • Added the new command rome lsp-proxy.
  • Added the new option--version as an alias for rome version
  • Added a new argument --files-max-size to change the allowed size of files, in bytes.
  • Added a new argument --formatter-enabled to the command rome ci.
  • Added a new argument --linter-enabled to the command rome ci.
  • Added the new format option --trailing-comma to configure where to add trailing commas.
  • Correctly show the supported options for rome ci, closes #​3456.
  • Fixed the command rome ci command to run the linter even if the formatter is disabled, closes #​3495.
  • Fixed the messaging of some diagnostics, #​3460.
Configuration
  • Added files.maxSize, to change the allowed size of files, in bytes.
Diagnostics
  • Fix false positive for unknown lint rule in suppression comments during formatting #​3406.
  • Correctly handle empty lines when printing code diffs #​3375.
Formatter
  • Added the new trailing comma option that configures where to add trailing commas. Supports the values: all, es5 and none; refer to the documentation to learn more.
  • Improved JSX formatting #​3499, #​3211, #​3377
  • Better formatting of object destructing
  • Improved formatting of test calls
  • Fixed formatting of trailing comments in arrow functions
Linter
  • BREAKING CHANGE: some rules have been moved to new groups to better reflect their purpose. This may result in Rome failing to load your configuration or suppression comments that now refer to unknown rules. Please check out #​3471 to learn more about the affected rules.
  • Fixed issues in the noUnreachable rule
  • Fixed false positive cases for noNegationElse #​3141
  • Fixed false positive cases for noUnusedVariables #​3169
  • Fixed an issue in our CFG #​3390
New rules
Parser
  • Improved messaging of diagnostics, using our new infrastructure
  • Fixed an issue where diagnostics couldn't be printed in WASM #​3349
  • Allow arguments in d.ts files #​3388
  • Fix parsing of less than in optional call chains #​3486
  • Fixed a case where export {"a"} from "b"; wasn't correctly parsed
VSCode
  • Make the "rename" command opt-in and use the VS Code provided "rename" feature that offers whole project renaming instead.
  • Added the new command Restart LSP Server
  • The LSP server is now able to listen to changes of rome.json and apply the new configuration

v3.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
  • 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
Formatter
BREAKING CHANGES
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:

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.

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
  • Fixed a poor diagnostic that was emitted when navigating a symbolic symbol #​3329
  • Added a size limit when inspecting files #​3330
Diagnostics
  • Do not print tabs and spaces for unchanged lines #​3327
VSCode
  • Fixed the calculation of text diffs inside the LSP #​3350

v0.10.0

Core
  • Rome is now faster and uses less memory on macOS and Linux systems! #​3237
  • We completely revamped our diagnostics! The new diagnostics allow us to give better information about the errors generated by Rome.
  • Greatly increased the performance of Rome's daemon, up to 300%! #​3151
Configuration

You can now ignore folders and files using the Unix shell style patterns:

{
  "formatter": {
    "ignore": ["scripts/*.js"]
  },
  "linter": {
    "ignore": ["src/**.test.{ts,js}"]
  }
}
Formatter
  • Completely revamped how the formatter handles comments and their placement inside the code #​3277
  • Improved formatting of intersection and unions types #​3162
  • Improved formatting of member chains #​3283
  • Improved formatting of call arguments #​3290
Linter
  • BREAKING CHANGE: This release changes the naming of the lint rule groups with the goal to make them language agnostic and avoid confusion among users and contributors.
    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
  • Added a new group called nursery, this group incubates new rules that are being developed.
  • Added a new group called style, this group incubates rules that orbits around styling.
  • Added a new group called correctness, this group incubates rules that orbits catching possible bugs.
  • Fixed a code action for useBlockStatements #​3199
  • Improved the rule useCamelCase #​3190 #​3210
  • Fixed invalid code action for useOptionalChain #​3257
  • Fixed bugs in noUnusedVariables #​3170, #​3316
New rules
Parser
  • Fixed an issue where the parser was not emitting a diagnostic on a certain TypeScript syntax #​3115
VSCode
  • The setting lspBin can be also expressed as relative path
  • The rules have been added to the configuration schema, allowing users to receive autocomplete
    when editing the rome.json for the rules section

Configuration

📅 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.


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

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

@renovate renovate bot changed the title chore(deps): update dependency rome to v11 Update dependency rome to v11 Dec 17, 2022
@renovate renovate bot changed the title Update dependency rome to v11 chore(deps): update dependency rome to v11 Dec 17, 2022
@renovate renovate bot changed the title chore(deps): update dependency rome to v11 chore(deps): update dependency rome to v11 - autoclosed Mar 28, 2023
@renovate renovate bot closed this Mar 28, 2023
@renovate renovate bot deleted the renovate/rome-11.x branch March 28, 2023 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants