Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Coverage remained the same at 82.941% when pulling 21a12a51dbd825abbfe475491c6ee63de93f7369 on depfu/update/npm/eslint-plugin-node-11.0.0 into c869183cc35ec1c958b92d2045c7894bf683c13d on master.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-plugin-node (^10.0.0 → ^11.0.0) · Repo
Release Notes
11.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
🔖 11.0.0
💥 update node/no-unsupported-features/es-builtins to recognize globalThis
💥 update rules to check `globalThis.*`
revert ESM support versions
💥 add check of bigint literal property names to node/no-unsupported-features/es-syntax
🐛 fix crash on dynamic import with identifier (#201)
✨ no-unsupported-features/node-builtins recognize backporting
✨ update no-deprecated-api rule for revoked deprecations
💥 update no-unsupported-features/node-builtins rule based on Node 13.2
✨ Node.js 13 supports ES modules
⚒ update CI.yml to add Node 13
Create FUNDING.yml
⚒ remove && because Windows doesn't support it
📝 fix wrong links
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands