Remove cypress from Shell dependencies

[rak-phillip]

Any project that consumes @rancher/shell inherits cypress as a transitive runtime dependency, including projects that have no need for it.

Proposed changes

• Remove cypress from dependencies in shell/package.json
• Remove the dead scripts: cy:run, cy:open, e2e:run, and e2e:dev from shell/package.json

Acceptance criteria

• cypress is removed from shell/package.json dependencies
• Scripts related to cypress are removed from shell/package.json
• yarn test:ci passes
• yarn build succeeds
• Downstream consumers of @rancher/shell no longer receive cypress as a transitive dependency

[github-actions]

🎯 Agentic Issue Triage

This is a well-scoped tech-debt cleanup task to remove cypress and related dead scripts from shell/package.json. Currently, any downstream consumer of @rancher/shell transitively receives cypress (a large, dev-only testing tool) as a runtime dependency — which is wasteful and unintended.

Confirmed from the codebase: cypress and eslint-plugin-cypress are present in shell/package.json dependencies, along with the scripts cy:run, cy:open, e2e:run, and e2e:dev.

📋 Subtask Checklist

• Remove cypress from dependencies in shell/package.json
• Remove eslint-plugin-cypress from dependencies in shell/package.json (also a cypress-related transitive dep)
• Remove scripts: cy:run, cy:open, e2e:run, e2e:dev from shell/package.json
• Verify e2e:pre script — remove or move if it's also dead
• Run yarn test:ci to confirm no unit test regressions
• Run yarn build to confirm build succeeds
• Optionally verify downstream extension scaffold no longer pulls in cypress via npm ls cypress or yarn why cypress

🔍 Debugging / Verification Strategy

1. After removing the entries, run:

   yarn install --frozen-lockfile
   yarn test:ci
   yarn build

2. To confirm cypress is no longer a transitive dep for downstream consumers, scaffold a test extension project and run:

   yarn why cypress

   It should report "not found".

3. Check if any file in shell/ imports from cypress directly:

   grep -r "from 'cypress'" shell/
   grep -r "require('cypress')" shell/

   If nothing references it, removal is safe.

💡 Notes for the Team

• cypress belongs in devDependencies of the root package.json only — it's an E2E test runner used at the monorepo root, not as a library shipped with @rancher/shell.
• eslint-plugin-cypress similarly should only live in devDependencies at the root if needed.
• The e2e:pre script in shell/package.json should be reviewed — it may also be a dead/misplaced script.
• This change is low-risk since no shell/ source code consumes cypress APIs; it only affects the package metadata.

Generated by Agentic Triage for issue #17831 · ● 169.8K · ◷

[github-actions]

🤖 Issue grooming analysis

All four primary grooming criteria are satisfied:

1. Clear Problem Statement ✅
The issue clearly explains the problem: any project consuming @rancher/shell currently inherits Cypress as an unneeded transitive runtime dependency.

2. Acceptance Criteria ✅
Five concrete, verifiable checklist items covering:

• Removal of Cypress from shell/package.json dependencies
• Removal of the dead Cypress-related scripts
• yarn test:ci passes
• yarn build succeeds
• Downstream consumers no longer receive Cypress as a transitive dependency

3. Technical Details ✅
Specific file (shell/package.json) and specific scripts (cy:run, cy:open, e2e:run, e2e:dev) are identified. Impact on downstream consumers is noted.

4. User Story / Flow ✅
This is a tech-debt task. The before/after state is clearly defined — no repro steps required.

5. Dependencies
No related issues or PRs referenced, but the issue is self-contained and independently actionable.

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ● 688.2K · ◷