michalsanger/Next.js Turbopack Bundle Size

Tracks bundle size changes across PRs for Next.js apps built with Turbopack

Trust Signals

workflow.ymlSHA-pinned

uses: michalsanger/nextjs-turbopack-bundle-size@ec880b8676c8e9859ce95aa51e910bb672388f76 # v1.8.0

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
github-token	GitHub token for downloading baseline artifact and posting PR comments	yes	—
stats-path	Path to the Turbopack stats file generated by the build. Auto-detects between .next/diagnostics/route-bundle-stats.json (Next.js 16.2+) and .next/server/webpack-stats.json (legacy).	no	.next/diagnostics/route-bundle-stats.json
artifact-name	Artifact name prefix used to store and retrieve the baseline stats. The branch name is appended automatically (e.g. turbopack-main-stats-main).	no	turbopack-main-stats
minimum-change-threshold	Byte threshold below which a size change is considered unchanged	no	0
budget-percent-increase-red	Percentage threshold for showing 🔴 on size increases. Increases above this percentage show 🔴, others show 🟡. Default 0 means all increases show 🔴.	no	0
app-name	Application name to display in the report header. When set, the sticky PR comment uses a unique header (bundle-size-report-{name}) so matrix jobs do not overwrite each other. If not set, a generic report header and the default comment key are used.	no	""
baseline-workflow	Workflow file name (e.g. main.yml) to look up the baseline artifact in. Useful when the baseline is produced by a different workflow than the one running this action. When unset, the artifact is searched in the current workflow.	no	""

no outputs