Skip to content

Publish usable source maps for production documentation bundles#3693

Open
reakaleek wants to merge 1 commit into
mainfrom
special-washer
Open

Publish usable source maps for production documentation bundles#3693
reakaleek wants to merge 1 commit into
mainfrom
special-washer

Conversation

@reakaleek

Copy link
Copy Markdown
Member

Why

Release documentation bundles advertise sourceMappingURL references, but .js.map / .css.map were only embedded in Debug builds. Production therefore served guaranteed 404s, which blocks Lighthouse and debugging tooling from attributing work to source modules (#3689).

What

Embed Parcel-generated JS and CSS source maps in all configurations so they ship alongside hashed bundles. Serving, cleanup of old hashed maps, and static extraction already supported .map files — only the Debug-only embed gate needed to change.

Closes #3689

Made with Cursor

Release bundles already advertise sourceMappingURL, but maps were only
embedded in Debug, so production tooling hit 404s (#3689).

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@Mpdreamz

Copy link
Copy Markdown
Member

We did this because old maps could acrue and we're being checked in. At some point our binary size started ballooning.

Are we sure parcel cleans up old versions properly now?

@reakaleek

Copy link
Copy Markdown
Member Author

We did this because old maps could acrue and we're being checked in. At some point our binary size started ballooning.

Are we sure parcel cleans up old versions properly now?

Will check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish usable source maps for production documentation bundles

2 participants