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 eslint-plugin-node to v11 #102

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 26, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-node 6.0.1 -> 11.1.0 age adoption passing confidence

Release Notes

mysticatea/eslint-plugin-node

v11.1.0

Compare Source

The many rules for Node.js in the ESLint core will be deprecated in ESLint 7.0.0. This release includes the clone of those core rules.

✨ Enhancements

v11.0.0

Compare Source

💥 Breaking changes

  • b6cb9a0 updated node/no-unsupported-features/node-builtins rule based on Node.js 13.2.0.
  • fb9ce15 updated node/no-unsupported-features/es-syntax rule to recognize BigInt literal property names.
  • 4295f6a updated the rules that check global variables to recognize globalThis.*.
  • 04051ed updated node/no-unsupported-features/es-builtins rule to recognize globalThis.

✨ Enhancements

  • 276a9ad updated node/no-deprecated-api rule to allow revoked deprecations.
  • 972f828 updated node/no-unsupported-features/node-builtins rule to handle backporting properly.

🐛 Bug fixes

  • 4f74fbf fixed a crash bug around dynamic import syntax.

v10.0.0

Compare Source

This release supports BigInt and Dynamic Imports if you are using ESLint 6.2.0 or later.

💥 Breaking Changes

  • 9ea67c9 updated node/no-unsupported-features/es-syntax rule to recognize BigInt literals and import().
  • b91b48d updated node/no-unsupported-features/es-builtins rule to recognize BigInt, BigInt64Array, BigUint64Array, and Promise.allSettled.
  • b57a4f9 updated node/file-extension-in-import, node/no-extraneous-import, node/no-missing-import, and node/no-unpublished-import rules to recognize import().
  • 4b9c4d7 updated node/no-deprecated-api rule to recognize module.createRequireFromPath.
  • 9c574ba updated plugin:node/recommended and the other configs.
    • It added node/no-exports-assign rule.
    • It changed exports global variable writable.
    • It enabled node/*-import rules in CommonJS mode as well.

✨ New rules

  • a0f0ee1 added node/no-exports-assign rule that disallows exports = {}.

v9.2.0

Compare Source

✨ New Rules

  • c1d5dbf added a new rule no-callback-literal.

🐛 Bug Fixes

  • 72de3a3 updated eslint-utils for security fix.

v9.1.0

Compare Source

✨ Features

  • fd9d19d updated no-deprecated-api to not suggest alternative APIs if it has not supported on configured Node.js version. Thank you, @​Lalem001 !

🐛 Bug Fixes

  • e5aee3c updated semver package to not crash on wildcard * version range.

v9.0.1

Compare Source

🐛 Bug Fixes

  • dfb4dc0 fixed the false positive of node/file-extension-in-import rule on scoped packages (#​160).

v9.0.0

Compare Source

Update for Node.js v12 🎉

💥 Breaking Changes

✨ New Rules

v8.0.1

Compare Source

🐛 Bug fixes

  • 62ba642 fixed the wrong messages of node/no-deprecated-api rule (#​142).
  • 0225b02...0593c67576c86b2cbf4990db38d1cc4707b2f309 fixed the false positives of no-unpublished-(bin|import|require) rules (#​115, #​126).

v8.0.0

Compare Source

This release focuses on supporting new things that were added between Node.js 8.7.0 and 11.0.0.

Breaking changes

  • 5860795 updated node/no-deprecated-api rule to disallow new deprecated APIs.
    Especially, it includes legacy URL API.
  • d153b93 updated node/no-unsupported-features/node-builtins rule to detect new APIs.

New rules

  • 46ed54d added node/prefer-global/text-decoder rule for new global varaible TextDecoder.
  • 46ed54d added node/prefer-global/text-encoder rule for new global varaible TextEncoder.

v7.0.1

Compare Source

Bug fixes

  • It fixed false positive that the node/no-unsupported-features/node-builtins reports the process.emitWarning method on Node.js >=6 <8. It was supported since Node.js 6.0.0.

v7.0.0

Compare Source

Breaking changes

New rules

Deprecated rules

Chore

I extracted the logic which detects certain globals and modules and those properties to the eslint-utils package. I wish it to be useful for your ESLint plugins.


All commits: 5260039...890ee63e98ef95ec5a27f50f42188102526d81b1


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.

@renovate renovate bot force-pushed the renovate/eslint-plugin-node-11.x branch from 9475056 to c001719 Compare January 11, 2020 09:26
@renovate renovate bot force-pushed the renovate/eslint-plugin-node-11.x branch from c001719 to 6650b5f Compare February 2, 2020 10:47
@renovate renovate bot force-pushed the renovate/eslint-plugin-node-11.x branch from 6650b5f to c893e77 Compare March 28, 2020 11:52
@renovate renovate bot force-pushed the renovate/eslint-plugin-node-11.x branch from c893e77 to 2094c2d Compare July 4, 2020 23:52
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant