Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/runtime-debug
Debug and verification workflow for runtime-bundle and module-resolution regressions.
Passed 21 of 22 test cases with the skill, and 10 of 22 without it.
and 15 more in the full report
13 fixed9 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Next.js local development, error overlay logs collapse internal framework frames into 'at ignore-listed frames'. What environment variable disables this ignore-list filtering in the dev server?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends setting __NEXT_SHOW_IGNORE_LISTED=true. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.
IS_WEBPACK_TEST=1 forces webpack (turbopack is default), NEXT_SKIP_ISOLATE=1 skips packing next.js.NEXT_SKIP_ISOLATE=1.Set __NEXT_SHOW_IGNORE_LISTED=true to disable the ignore-list filtering in dev server error output. By default, Next.js collapses internal frames to at ignore-listed frames, which hides useful context when debugging framework internals. Defined in packages/next/src/server/patch-error-inspect.ts.
When user next build starts bundling internal Node-only helpers unexpectedly:
.next/server/.../page.js.nft.json).next/dist/server/stream-utils/node-stream-helpers.js, node:stream/promises).test-start-webpack assertion that reads the route trace and traced server chunks, and fails on forbidden internals. This validates user-project bundling (not publish-time runtime bundling).To prove what user bundling includes, emit webpack stats from the app's next.config.js:
// next.config.js
module.exports = {
webpack(config) {
config.profile = true
return config
},
}
Then use stats.toJson({ modules: true, chunks: true, reasons: true }) and diff webpack-stats-server.json between modes. This gives concrete inclusion reasons (e.g. which module required node:stream/promises) and is more reliable than analyzer HTML alone.
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.