mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-14 02:42:24 +03:00
8e2fb04329
The v3.8.50 staged publish was refused by the registry: npm error code E413 npm error 413 Payload Too Large - POST https://registry.npmjs.org/-/stage/package/omniroute The tarball had reached 288.7 MB packed / 1.1 GB unpacked, against 174.5 MB / 792.3 MB for the 3.8.49 that published fine. 842 *.nft.json files accounted for 668.7 MB of that — 61% of the whole package — having doubled from the 325.0 MB across 748 files shipped in 3.8.49. Those are Next.js Node File Trace manifests: build-time metadata used to compute the standalone bundle, never read while serving. Nothing under src/, open-sse/ or bin/ references them, which the new test pins. Excluding them follows the negation pattern files[] already uses for node_modules and test sources. Verified against an isolated package that the glob drops page.js.nft.json while keeping page.js and other.json, so it does not over-match. Separately worth tracking: the compiled JS under dist/.build/next also grew 69% between 3.8.49 and 3.8.50 (231.9 MB to 391.9 MB, +3695 files). That is not what broke the publish and is left for its own investigation.