Skip to content

improve(javascript-pro): modernize runtime, tooling, and framework coverage#560

Merged
davila7 merged 1 commit into
mainfrom
review/javascript-pro-2026-05-02
May 2, 2026
Merged

improve(javascript-pro): modernize runtime, tooling, and framework coverage#560
davila7 merged 1 commit into
mainfrom
review/javascript-pro-2026-05-02

Conversation

@davila7
Copy link
Copy Markdown
Owner

@davila7 davila7 commented May 2, 2026

Automated Component Improvement

Component: cli-tool/components/agents/programming-languages/javascript-pro.md
Downloads: 3,837 total | 299/week (2nd most downloaded agent)

Changes

  1. Runtime version baseline updated — Persona upgraded from Node.js 20+ to Node.js 22 LTS / Node.js 24 LTS. ES mastery updated from ES2023 to ES2025 with new features: Object.groupBy(), Promise.withResolvers(), Set methods, Iterator helpers, RegExp.escape(), explicit resource management (using/await using).

  2. New Runtime ecosystem section — Added coverage of Node.js 22/24 key additions (native fetch, built-in test runner, native TypeScript type-stripping in Node 24), Bun (2-4x performance, native TS), and Deno 2.x (npm-compatible, security-by-default) with guidance on when to choose each.

  3. Vitest promoted as default test runner — Restructured Testing methodology: Vitest leads for new projects (native ESM/TS, 10-20x faster), Jest retained for legacy/React Native, Playwright added for E2E, node:test for library authors.

  4. Build tooling modernized — Vite 6/7/8 (Rolldown-powered) becomes the default recommendation. Added Turbopack (Next.js 15 stable), Rolldown (standalone), esbuild. Webpack demoted to legacy/maintenance-mode.

  5. Modern framework patterns section added — React 19 (Compiler, Server Components, Actions API, use() hook), Next.js 15 (Turbopack, partial prerendering), Vue 3.5/3.6 (Vapor Mode), Svelte 5 (Runes), SolidJS.

  6. New Package management section — npm workspaces + --provenance, pnpm strict isolation, Bun fastest installs, package.json exports field for ESM/CJS dual publishing, ignore-scripts=true, lockfile CI verification.

  7. Security section expanded for supply-chain threats — Added Socket.dev/Snyk behavioral analysis, ignore-scripts=true in .npmrc, lockfile verification in CI, typosquatting awareness (per CISA Sep 2025 alert).

  8. Description example updated — Third example now references Vitest instead of Jest for consistency with the improved system prompt.

Research Summary

The agent was directing users toward approaching end-of-life runtimes (Node.js 20 EOL April 2026 is close), outdated tooling (Webpack is maintenance-mode, Vite now 17M weekly downloads), and superseded test runner defaults (Vitest exceeds Jest in 2025 State of JS satisfaction). With 3,837 downloads and ~299/week, stale guidance here had significant impact.

Validation

  • All required frontmatter fields present (name, description, tools)
  • kebab-case filename: javascript-pro.md
  • No hardcoded secrets or API keys
  • No absolute paths
  • Correct category: programming-languages
  • component-reviewer: PASSED

Automated review cycle by Component Improvement Loop


Summary by cubic

Modernizes the javascript-pro component to Node.js 22/24 and ES2025, and updates guidance across runtimes, testing, bundling, and frameworks. Keeps users on current, faster, and more secure defaults.

  • Refactors
    • Area: components (cli-tool/components/); updated agents/programming-languages/javascript-pro.md. No new components; catalog (docs/components.json) unchanged; no new environment variables or secrets.
    • Runtime and language: baseline moved to Node.js 22/24 and ES2025 with modern APIs; added ecosystem guidance for Node.js, Bun, and Deno 2.x.
    • Testing: default Vitest; Jest for legacy/React Native; Playwright for E2E; node:test for library authors.
    • Build: Vite 6/7/8 (Rolldown) as default; Turbopack for Next.js 15; Rolldown; esbuild; Webpack marked legacy.
    • Frameworks, packages, security: patterns for React 19, Next.js 15, Vue 3.5/3.6, Svelte 5, SolidJS; updated npm/pnpm/Bun guidance (--provenance, exports, ignore-scripts=true, lockfile verification); supply-chain checks with Socket.dev/Snyk.

Written for commit 7488375. Summary will update on new commits.

…verage

- Update persona from Node.js 20+ to Node.js 22 LTS / Node.js 24 LTS
- Expand ES mastery from ES2023 to ES2025 (Object.groupBy, Promise.withResolvers, Set methods, Iterator helpers, RegExp.escape, explicit resource management)
- Add Runtime ecosystem section covering Node.js 22/24, Bun, and Deno 2.x
- Replace Jest-first testing with Vitest as default; add Playwright for E2E and node:test for library authors
- Modernize Build and tooling: Vite 6/7/8 (Rolldown-powered) as default, Turbopack, Rolldown, esbuild; demote Webpack to legacy
- Add Modern framework patterns section: React 19, Next.js 15, Vue 3.5/3.6, Svelte 5, SolidJS
- Add Package management section: npm workspaces, pnpm, Bun, exports field, provenance
- Expand Security practices with Socket.dev/Snyk, ignore-scripts, lockfile CI verification, typosquatting awareness
- Update third description example to reference Vitest instead of Jest

Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
aitmpl-dashboard Ready Ready Preview, Comment May 2, 2026 8:17pm
claude-code-templates Ready Ready Preview, Comment May 2, 2026 8:17pm

@github-actions github-actions Bot added the review-pending Component PR awaiting maintainer review label May 2, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

👋 Thanks for contributing, @davila7!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

  1. 🤖 Automated security audit runs and posts results on this PR.
  2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
  3. Merge — once approved, your PR is merged to main.
  4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
  5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

  • Check the Security Audit comment below for any issues to fix.
  • Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

⚠️ Security Audit Report

Status: ❌ FAILED

Metric Count
Total Components 763
✅ Passed 360
❌ Failed 403
⚠️ Warnings 1006

❌ Failed Components (Top 5)

Component Errors Warnings Score
vercel-edge-function 3 4 81/100
prompt-engineer 2 0 90/100
neon-expert 2 2 88/100
agent-overview 2 1 89/100
unused-code-cleaner 2 1 89/100

...and 398 more failed component(s)


📊 View Full Report for detailed error messages and all components

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 issues found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="cli-tool/components/agents/programming-languages/javascript-pro.md">

<violation number="1" location="cli-tool/components/agents/programming-languages/javascript-pro.md:44">
P2: This line overstates Node 24 TypeScript type-stripping as stable; Node docs mark it as release-candidate in Node 24 and only mark it stable in Node 25.2+.</violation>

<violation number="2" location="cli-tool/components/agents/programming-languages/javascript-pro.md:132">
P2: `Vite 6/7/8 (Rolldown-powered)` is inaccurate: for Vite 6/7, Rolldown is an experimental opt-in package, while Vite 8 is the version with integrated Rolldown by default.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.


Runtime ecosystem:
- Node.js 22 LTS: stable Web Streams, built-in test runner, native fetch, improved ESM/CJS interop
- Node.js 24 LTS: native TypeScript type-stripping stable, updated V8 engine, performance improvements
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: This line overstates Node 24 TypeScript type-stripping as stable; Node docs mark it as release-candidate in Node 24 and only mark it stable in Node 25.2+.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/agents/programming-languages/javascript-pro.md, line 44:

<comment>This line overstates Node 24 TypeScript type-stripping as stable; Node docs mark it as release-candidate in Node 24 and only mark it stable in Node 25.2+.</comment>

<file context>
@@ -24,14 +24,27 @@ JavaScript development checklist:
+
+Runtime ecosystem:
+- Node.js 22 LTS: stable Web Streams, built-in test runner, native fetch, improved ESM/CJS interop
+- Node.js 24 LTS: native TypeScript type-stripping stable, updated V8 engine, performance improvements
+- Bun: 2-4x faster installs and execution, native TypeScript support, built-in bundler and test runner
+- Deno 2.x: npm-compatible, security-by-default with explicit permissions, excellent TypeScript support
</file context>
Suggested change
- Node.js 24 LTS: native TypeScript type-stripping stable, updated V8 engine, performance improvements
- Node.js 24 LTS: native TypeScript type-stripping enabled by default (release-candidate in v24), updated V8 engine, performance improvements

- Webpack optimization
- Rollup for libraries
- ESBuild integration
- Vite 6/7/8 (Rolldown-powered): default choice for new projects, 7x faster cold starts
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Vite 6/7/8 (Rolldown-powered) is inaccurate: for Vite 6/7, Rolldown is an experimental opt-in package, while Vite 8 is the version with integrated Rolldown by default.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/agents/programming-languages/javascript-pro.md, line 132:

<comment>`Vite 6/7/8 (Rolldown-powered)` is inaccurate: for Vite 6/7, Rolldown is an experimental opt-in package, while Vite 8 is the version with integrated Rolldown by default.</comment>

<file context>
@@ -93,26 +108,46 @@ Browser API mastery:
-- Webpack optimization
-- Rollup for libraries
-- ESBuild integration
+- Vite 6/7/8 (Rolldown-powered): default choice for new projects, 7x faster cold starts
+- Turbopack: Next.js 15 default bundler, stable for production
+- Rolldown: standalone Rust-based bundler compatible with Rollup plugin ecosystem
</file context>
Suggested change
- Vite 6/7/8 (Rolldown-powered): default choice for new projects, 7x faster cold starts
- Vite 8 (Rolldown-powered): default choice for new projects; for Vite 6/7, Rolldown is available via the experimental rolldown-vite package

@davila7 davila7 merged commit f75f4e8 into main May 2, 2026
7 checks passed
@davila7 davila7 deleted the review/javascript-pro-2026-05-02 branch May 2, 2026 21:09
davila7 added a commit that referenced this pull request May 2, 2026
Reflects merged improvements to cli-tool/components/agents/programming-languages/javascript-pro.md.

Automated by pr-verification cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-pending Component PR awaiting maintainer review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant