jo3-l / obscenity

Robust, extensible profanity filter for NodeJS
MIT License
70 stars 2 forks source link

chore(deps): update dependency eslint-plugin-simple-import-sort to v10 #25

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-simple-import-sort ^7.0.0 -> ^10.0.0 age adoption passing confidence

Release Notes

lydell/eslint-plugin-simple-import-sort ### [`v10.0.0`](https://togithub.com/lydell/eslint-plugin-simple-import-sort/blob/HEAD/CHANGELOG.md#Version-1000-2023-01-27) [Compare Source](https://togithub.com/lydell/eslint-plugin-simple-import-sort/compare/v9.0.0...v10.0.0) This release might move some imported items with `type` around. This is a breaking formatting change (that only affects TypeScript and Flow), but only in the form of that you need to autofix your files. In previous versions, `type` specifiers came first: ```ts import { type B, a } from "a"; export { type B, a } from "a"; ``` Now, all specifiers are sorted alphabetically, regardless of `type`: ```ts import { a, type B } from "a"; export { a, type B } from "a"; ``` Motivation: You might import a class for a type annotation using: ```ts import { type MyClass, coolFunction, } from "example"; ``` Later, you also start instantiating that class in the same file (`new MyClass()`), so you remove `type`. Previously, this resulted in a messy diff due to the class moving: ```diff import { - type MyClass, coolFunction, + MyClass, } from "example"; ``` Now, the sorting with the `type` keyword would be: ```ts import { coolFunction, type MyClass, } from "example"; ``` Now there’s no reordering diff, just the `type` keyword being removed: ```diff import { coolFunction, - type MyClass, + MyClass, } from "example"; ``` This is consistent with \[“Why sort on `from`?”]\[sort-from]. Thanks to Jake Bailey ([@​jakebailey](https://togithub.com/jakebailey)) for reporting and suggesting the fix! ### [`v9.0.0`](https://togithub.com/lydell/eslint-plugin-simple-import-sort/blob/HEAD/CHANGELOG.md#Version-900-2023-01-16) [Compare Source](https://togithub.com/lydell/eslint-plugin-simple-import-sort/compare/v8.0.0...v9.0.0) This version adds support for \[eslint-plugin-svelte], and for `declare module` in TypeScript. More generally, imports and exports are now supported *anywhere,* by finding the set of parents of all imports and exports and working with those. Previously, the plugin only sorted imports and exports directly inside a `Program` node. For eslint-plugin-svelte and `declare module` that didn’t cut it. This is only a breaking change if you imports or exports in `declare module` in TypeScript, and only in the form of that you need to autofix your files. ### [`v8.0.0`](https://togithub.com/lydell/eslint-plugin-simple-import-sort/blob/HEAD/CHANGELOG.md#Version-800-2022-09-03) [Compare Source](https://togithub.com/lydell/eslint-plugin-simple-import-sort/compare/v7.0.0...v8.0.0) Node.js builtin modules prefixed with `node:` are now in a separate group by default (regex: `^node:`), above the packages group. (Node.js builtins *without* `node:` are still sorted together with npm packages like before.) Before: ```js import fs from "fs"; import _ from "lodash-es"; import { rmSync } from "node:fs"; ``` After: ```js import { rmSync } from "node:fs"; import fs from "fs"; import _ from "lodash-es"; ``` This is only a breaking change if you use the `node:` prefix in imports, and only in the form of that you need to autofix your files.

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 is behind base branch, 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.

renovate[bot] commented 1 year ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.