Skip to content
This repository was archived by the owner on Jan 16, 2026. It is now read-only.

chore(deps): update dependency eslint-plugin-n to v17#241

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-n-17.x
Closed

chore(deps): update dependency eslint-plugin-n to v17#241
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-n-17.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 31, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-n ^16.0.0 -> ^17.0.0 age adoption passing confidence

Release Notes

eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.7.0

Compare Source

🌟 Features
  • hashbang: Add support to map extensions to executables (#​278) (3fd7639)
  • node-builtin: Add node 20.13.0, 22.0.0, and 22.1.0 support (#​276) (4a685c0)
🩹 Fixes
  • node-builtins: Remove "node:" prefix from "ignores" message (#​277) (704f0b9)
📚 Documentation
  • node-builtins: Specify that only static properties are supported (#​272) (735a520)
  • Provide an example with eslint-plugin-n to Playground (#​275) (cb8ffa6)

v17.6.0

Compare Source

🌟 Features
📚 Documentation

v17.5.1

Compare Source

🩹 Fixes

v17.5.0

Compare Source

🌟 Features
🩹 Fixes
🧹 Chores

v17.4.0

Compare Source

🌟 Features
🩹 Fixes
  • unsupported-features/node-builtins-modules version comparation (#​257) (5c67787)
🧹 Chores

v17.3.1: Release 17.3.1

Compare Source

  • Revert "fix: unsupported-features/node-builtins-modules range compare" (#​254) (caecf3e)

v17.3.0

Compare Source

🌟 Features
🩹 Fixes
  • unsupported-features/node-builtins-modules range compare (#​252) (d50ae85)
🧹 Chores

v17.2.1

Compare Source

🩹 Fixes
🧹 Chores

v17.2.0

Compare Source

🌟 Features
  • no-missing-imports: add tryExtensions option (#​228) (ae5329c)
  • no-unsupported-features: ✨ Update to node v20.12.0/v21.7.0 (#​229) (a8d0539)
🩹 Fixes

v17.1.0

Compare Source

🌟 Features
📚 Documentation

v17.0.0

Compare Source

Chores
  • use ts-ignore-import to lighten the dependencies (#​219) (fb0aaae)

Configuration

📅 Schedule: Branch creation - "on friday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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
Contributor Author

renovate bot commented May 31, 2024

⚠️ 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 click 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: package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: eslint-config-standard@17.1.0
npm warn Found: eslint-plugin-n@17.9.0
npm warn node_modules/eslint-plugin-n
npm warn   dev eslint-plugin-n@"^17.0.0" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint-plugin-n@"^15.0.0 || ^16.0.0 " from eslint-config-standard@17.1.0
npm warn node_modules/eslint-config-standard
npm warn   eslint-config-standard@"17.1.0" from eslint-config-standard-with-typescript@40.0.0
npm warn   node_modules/eslint-config-standard-with-typescript
npm warn
npm warn Conflicting peer dependency: eslint-plugin-n@16.6.2
npm warn node_modules/eslint-plugin-n
npm warn   peer eslint-plugin-n@"^15.0.0 || ^16.0.0 " from eslint-config-standard@17.1.0
npm warn   node_modules/eslint-config-standard
npm warn     eslint-config-standard@"17.1.0" from eslint-config-standard-with-typescript@40.0.0
npm warn     node_modules/eslint-config-standard-with-typescript
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-standard-with-typescript@40.0.0
npm error Found: eslint-plugin-n@17.9.0
npm error node_modules/eslint-plugin-n
npm error   dev eslint-plugin-n@"^17.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint-plugin-n@"^15.0.0 || ^16.0.0 " from eslint-config-standard-with-typescript@40.0.0
npm error node_modules/eslint-config-standard-with-typescript
npm error   dev eslint-config-standard-with-typescript@"^40.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint-plugin-n@16.6.2
npm error node_modules/eslint-plugin-n
npm error   peer eslint-plugin-n@"^15.0.0 || ^16.0.0 " from eslint-config-standard-with-typescript@40.0.0
npm error   node_modules/eslint-config-standard-with-typescript
npm error     dev eslint-config-standard-with-typescript@"^40.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-07-19T08_53_55_903Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-19T08_53_55_903Z-debug-0.log

@coderabbitai
Copy link

coderabbitai bot commented May 31, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch 6 times, most recently from b227c8a to f54c353 Compare June 7, 2024 09:07
@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch 3 times, most recently from c6df0ac to e477446 Compare June 14, 2024 03:58
@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch 6 times, most recently from 2f69dc0 to 1fe7e46 Compare June 28, 2024 03:32
@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch 6 times, most recently from e5ed16b to a61ca12 Compare July 8, 2024 03:32
@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch 3 times, most recently from e852546 to 463db98 Compare July 15, 2024 03:53
@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch from 463db98 to 62af8e7 Compare July 19, 2024 05:27
@renovate renovate bot force-pushed the renovate/eslint-plugin-n-17.x branch from 62af8e7 to 0f079b9 Compare July 19, 2024 08:41
@joshlopes joshlopes closed this Jul 19, 2024
@renovate
Copy link
Contributor Author

renovate bot commented Jul 19, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 17.x releases. But if you manually upgrade to 17.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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant