Update ESLint pipedream plugin used to new scoped package

[js07]

WHY

The eslint-pipedream-plugin npm package has been deprecated and replaced with the new scoped package @pipedream/eslint-plugin-pipedream.

v0.2.5 allows the dir prop to omit description and label properties.

Summary by CodeRabbit

• Chores
  • Updated ESLint plugin dependency to use the new scoped package version for improved compatibility and maintenance. No changes to user-facing functionality.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Jun 25, 2025 9:49pm
pipedream-docs	⬜️ Ignored (Inspect)			Jun 25, 2025 9:49pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jun 25, 2025 9:49pm

[coderabbitai]

Walkthrough

The changes update the ESLint plugin for Pipedream by replacing the unscoped package with its new scoped version in both the ESLint configuration and the development dependencies. No other code, rules, or configurations were altered.

Changes

File(s)	Change Summary
eslint.config.mjs	Updated import statement to use @pipedream/eslint-plugin-pipedream instead of eslint-plugin-pipedream.
package.json	Replaced eslint-plugin-pipedream (0.2.4) with @pipedream/eslint-plugin-pipedream (0.2.5) in devDependencies.

Poem

A new plugin hops into view,
Scoped and shiny, version new!
The config’s path is now precise,
With pipedream’s rules—oh, how nice!
Dependencies pruned, the garden neat,
ESLint’s tune is now complete.
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

eslint.config.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 74c6128 and 3b592b8.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• eslint.config.mjs (1 hunks)
• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base

🔇 Additional comments (2)

package.json (1)

41-46: Double-check that the deprecated eslint-plugin-pipedream package is fully removed

The new scoped plugin is added correctly, but please confirm that
eslint-plugin-pipedream is no longer listed anywhere in devDependencies, lockfiles, or CI caches to prevent duplicate resolution / version drift.

#!/usr/bin/env bash
# Find lingering references to the deprecated package
rg -n '"eslint-plugin-pipedream"' || echo "✅  no occurrences found"

eslint.config.mjs (1)

1-4: Import statement update looks good

The switch to @pipedream/eslint-plugin-pipedream aligns with the dependency change and the plugin identifier (pipedream) remains consistent in the plugins map. No further action needed.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.