chore(deps-dev): bump @nullvoxpopuli/eslint-configs from 2.2.46 to 3.0.4

[dependabot]

Bumps @nullvoxpopuli/eslint-configs from 2.2.46 to 3.0.4.

Release notes

Sourced from @​nullvoxpopuli/eslint-configs's releases.

@​nullvoxpopuli/eslint-configs@​3.0.4

Patch Changes

• ed3496e Thanks @​NullVoxPopuli! - widen range of @​typescript-eslint peers

@​nullvoxpopuli/eslint-configs@​3.0.3

Patch Changes

• #328 5e62c88 Thanks @​NullVoxPopuli! - disable accidentally enabled lint rule, import/exports-last

@​nullvoxpopuli/eslint-configs@​3.0.2

Patch Changes

• #323 9ddd667 Thanks @​NullVoxPopuli! - Rule fixes which affect typescript and ember projects:

  in Ember projects, node files will be linted assuming at least Node 16. (Node 16 is already a requirement to use eslint-configs v3)

  in TypeScript projects, the "ban-types" lint has been turned off. In my experience writing libraries, there are many cases where "basic type and you just don't care, becausue it doesn't affect intellisense" is the right choice -- these types include object and Function, for example, and should be allowed. It's true that using different types that are more specific would provide better intellisense, if they are user facing -- but for non-user-facing types, these types are perfectly fine.

@​nullvoxpopuli/eslint-configs@​3.0.1

Patch Changes

• #319 e29a127 Thanks @​NullVoxPopuli! - in ember's deprecation-worflow.js, allow the "self" global

@​nullvoxpopuli/eslint-configs@​3.0.0

Major Changes

• f1a1f30 Thanks @​NullVoxPopuli! - prettier integration with all exported configs is now off by default.

  To get the old behavior back, pass prettierIntegration: true in the config object to each config helper.

  const { configs } = require('@nullvoxpopuli/eslint-configs');
  module.exports = configs.ember({ prettierIntegration: true });

  or

  const { configs } = require('@nullvoxpopuli/eslint-configs');

... (truncated)

Changelog

Sourced from @​nullvoxpopuli/eslint-configs's changelog.

3.0.4

Patch Changes

• ed3496e Thanks @​NullVoxPopuli! - widen range of @​typescript-eslint peers

3.0.3

Patch Changes

• #328 5e62c88 Thanks @​NullVoxPopuli! - disable accidentally enabled lint rule, import/exports-last

3.0.2

Patch Changes

• #323 9ddd667 Thanks @​NullVoxPopuli! - Rule fixes which affect typescript and ember projects:

  in Ember projects, node files will be linted assuming at least Node 16. (Node 16 is already a requirement to use eslint-configs v3)

  in TypeScript projects, the "ban-types" lint has been turned off. In my experience writing libraries, there are many cases where "basic type and you just don't care, becausue it doesn't affect intellisense" is the right choice -- these types include object and Function, for example, and should be allowed. It's true that using different types that are more specific would provide better intellisense, if they are user facing -- but for non-user-facing types, these types are perfectly fine.

3.0.1

Patch Changes

• #319 e29a127 Thanks @​NullVoxPopuli! - in ember's deprecation-worflow.js, allow the "self" global

3.0.0

Major Changes

• f1a1f30 Thanks @​NullVoxPopuli! - prettier integration with all exported configs is now off by default.

  To get the old behavior back, pass prettierIntegration: true in the config object to each config helper.

  const { configs } = require('@nullvoxpopuli/eslint-configs');
  module.exports = configs.ember({ prettierIntegration: true });

... (truncated)

Commits

• 9c5d27a Merge pull request #332 from NullVoxPopuli/changeset-release/main
• 9bedd44 Version Packages
• ed3496e Add changeset
• 8542662 Fix peer deps' range
• 06bbb11 Merge pull request #329 from NullVoxPopuli/changeset-release/main
• 2396488 Version Packages
• 3d5656b Merge pull request #328 from NullVoxPopuli/disable-import-rule
• 5e62c88 Disable import lint rule
• a23fc27 chore(deps): update dependency eslint-plugin-ember to v11.4.3
• 6b8738d chore(deps): update dependency eslint to v8.32.0
• 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 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)

[dependabot]

Superseded by #554.