'rtk npm run build' is expecting to be run as 'rtk npm build', which confuses the LLM #438
Description
When using 'rtk npm run build' to build a standard mode & next.js application, The following error is output, indicating that this is being run as 'npm run run build':
npm error Missing script: "run"
npm error
npm error To see a list of scripts, run:
npm error npm run
npm error A complete log of this run can be found in: ***-debug-0.log
Running it as 'rtk npm build' works, but this is non-standard and confuses the LLM as well as the developer.
Additionally, the output from rtk running this is bigger than the original (818 vs 669 chars) - Happy to raise this as a separate issue if needed. Output details below:
$ rtk npm build
> next build
▲ Next.js 16.1.4 (Turbopack)
- Environments: .env.local
Creating an optimized production build ...
✓ Compiled successfully in 6.2s
Running TypeScript ...
Collecting page data using 15 workers ...
Generating static pages using 15 workers (0/11) ...
Generating static pages using 15 workers (2/11)
Generating static pages using 15 workers (5/11)
Generating static pages using 15 workers (8/11)
✓ Generating static pages using 15 workers (11/11) in 463.1ms
Finalizing page optimization ...
Route (app)
// ** Removed for privacy
ƒ Proxy (Middleware)
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand
$ npm run build
> suite-app@0.1.0 build
> next build
▲ Next.js 16.1.4 (Turbopack)
- Environments: .env.local
Creating an optimized production build ...
✓ Compiled successfully in 6.5s
✓ Finished TypeScript in 5.2s
✓ Collecting page data using 15 workers in 655.1ms
✓ Generating static pages using 15 workers (11/11) in 493.6ms
✓ Finalizing page optimization in 394.6ms
Route (app)
// ** Removed for privacy
ƒ Proxy (Middleware)
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand
My environment: WSL (Ubuntu) with Vscode + Claude code extension and GLM-5