List the exact source file paths you can see in this repository and what each does.
List the exact source file paths you can see in this repository and what each do
About vercel/next.js · 2 messages · last activity 3 Jul 2026
Based on the repository data provided, here are the exact source file paths visible:
-
[packages/next/src/bin/next.ts] — The CLI entry point for Next.js. Defines command handlers for
build,experimental-analyze, andstatic-routes-infocommands with their options and arguments. Examples include build options like--turbo,--debug,--profile, and the experimental analyzer setup [packages/next/src/bin/next.ts:L182-L301, L742-L772]. -
[packages/next/src/cli/internal/static-routes-info.js] — Imported dynamically to handle the
static-routes-infoCLI command. Exports thestaticRoutesInfoClifunction that processes route information with sorting and filtering options. -
[packages/next/src/cli/next-analyze.js] — Imported dynamically to handle the
experimental-analyzecommand, which analyzes production bundle output with an interactive web UI (Turbopack-only). -
[packages/next/src/bundles/webpack/packages/HotModuleReplacement.runtime.js] — Webpack's Hot Module Replacement (HMR) runtime implementation. Contains functions like
hotCheck(),hotApply(),internalApply(), andtrackBlockingPromise()that manage the HMR state machine and module updates [packages/next/src/bundles/webpack/packages/HotModuleReplacement.runtime.js:L259-L352]. -
[packages/next/src/bundles/webpack/packages/SourceMapDevToolModuleOptionsPlugin.js] — A webpack plugin module that re-exports
SourceMapDevToolModuleOptionsPluginfrom webpack [packages/next/src/bundles/webpack/packages/SourceMapDevToolModuleOptionsPlugin.js:L1-L2].
Did this answer what you came for?
Want to ask your own question?
Open chat for vercel/next.jsPublic Q&A. Generated by RepoPilot from the actual source of vercel/next.js. AI answers can be incomplete or stale — verify before relying on them.