build(deps-dev): bump prettier-plugin-sort-json from 3.1.0 to 4.0.0

[dependabot]

Bumps prettier-plugin-sort-json from 3.1.0 to 4.0.0.

Release notes

Sourced from prettier-plugin-sort-json's releases.

4.0.0

Changed

• BREAKING: Drop support for Node.js v16 (#203)
• BREAKING: Update case insensitive sort to use deterministic key order (#189)
  • Previously the "case insensitive" sorting options would leave keys in their original order when they differed only in case. They have been updated to sort identical keys in case order instead, making these sort options deterministic.
  • This change has been made because deterministic sort orders tend to be easier to work with, are more aligned with how Prettier works, and typically lead to less churn. However, if your project needs to preserve original key order, you can emulate the old behavior by defining a custom sort order that has a category for each case-insensitive character. For example, you could set this as your prettierrc.js file:

    {
        jsonSortOrder: JSON.stringify({
            '/^[Aa]/': 'none',
            '/^[Bb]/': 'none',
            '/^[Cc]/': 'none',
            ...
            '/^[Zz]/': 'none',
        })
    }

  This should work for small character sets. If you require case-insensitive sorting with a larger character set, please submit a feature request. We can bring back the old sorting order as an option if there is demand for it.

Changelog

Sourced from prettier-plugin-sort-json's changelog.

[4.0.0]

Changed

• BREAKING: Drop support for Node.js v16 (#203)
• BREAKING: Update case insensitive sort to use deterministic key order (#189)
  • Previously the "case insensitive" sorting options would leave keys in their original order when they differed only in case. They have been updated to sort identical keys in case order instead, making these sort options deterministic.
  • This change has been made because deterministic sort orders tend to be easier to work with, are more aligned with how Prettier works, and typically lead to less churn. However, if your project needs to preserve original key order, you can emulate the old behavior by defining a custom sort order that has a category for each case-insensitive character. For example, you could set this as your prettierrc.js file:

    {
        jsonSortOrder: JSON.stringify({
            '/^[Aa]/': 'none',
            '/^[Bb]/': 'none',
            '/^[Cc]/': 'none',
            ...
            '/^[Zz]/': 'none',
        })
    }

  This should work for small character sets. If you require case-insensitive sorting with a larger character set, please submit a feature request. We can bring back the old sorting order as an option if there is demand for it.

Commits

• fcf9d7b 4.0.0 (#205)
• cb69326 chore(deps): update yarn to v4 (#188)
• af521fd Reduce Renovate frequency to once-per-hour (#204)
• ad086f7 chore(deps): update dependency ava to v6 (#190)
• e0ef1c5 Drop support for Node.js v16 (#203)
• 2d305da Support case variants for insensitive lexical sort (#189)
• 2a95264 chore(deps): update dependency @​lavamoat/allow-scripts to v3 (#187)
• 24dff74 chore(deps): update dependency typescript to v5 (#183)
• cc771de chore(deps): update minor (#184)
• fc385ca Exclude Prettier from grouped Renovate update (#200)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coveralls]

Pull Request Test Coverage Report for Build 8333628014

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 45.307%

---

Totals
Change from base Build 8243212637:	0.0%
Covered Lines:	174
Relevant Lines:	358

---

💛 - Coveralls