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

Update dependency eslint-plugin-node to v11 #196

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 30, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-node ^8.0.0 -> ^11.0.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


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
Copy link
Author

renovate bot commented Dec 30, 2019

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you check the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
warning stylelint > postcss-markdown > remark > unified > @types/vfile > @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
warning typescript-eslint-parser > typescript-estree@5.3.0: This package was moved to @typescript-eslint/typescript-estree, please install the latest version from there instead
lerna notice cli v3.14.1
lerna info Bootstrapping 5 packages
lerna info Installing external dependencies
lerna ERR! npm install --ignore-scripts --ignore-engines --ignore-platform --mutex network:31879 exited 1 in '@takasho/eslint-config-flowtype'
lerna ERR! npm install --ignore-scripts --ignore-engines --ignore-platform --mutex network:31879 stderr:
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "network:": network:31879

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2019-12-30T16_58_58_115Z-debug.log

lerna ERR! npm install --ignore-scripts --ignore-engines --ignore-platform --mutex network:31879 exited 1 in '@takasho/eslint-config-flowtype'

@renovate
Copy link
Author

renovate bot commented Mar 25, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant