mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 00:09:23 +02:00
[PR #5] [MERGED] fix: inline source content in sourcemaps to prevent missing source warnings #238
Labels
No labels
enhancement
enhancement
good first issue
help wanted
nextjs-tracking
nextjs-tracking
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vinext#238
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/cloudflare/vinext/pull/5
Author: @threepointone
Created: 2/24/2026
Status: ✅ Merged
Merged: 2/24/2026
Merged by: @southpolesteve
Base:
main← Head:fix/inline-sourcemap-sources📝 Commits (1)
747ac78fix: inline source content in sourcemaps to prevent missing source warnings📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
tsconfig.json(+1 -0)📄 Description
Problem
When vinext is installed from npm, Vite logs many warnings during dev:
The published
dist/includes.js.mapfiles that reference the original.tssource files via"sources", but the.tsfiles aren't included in the npm package.Fix
Adds
"inlineSources": truetotsconfig.json. This tellstscto embed the original TypeScript source content directly in the.js.mapfiles viasourcesContent, so no separate source files are needed.Verified: after building,
.js.mapfiles now containsourcesContentwith the full original source.Fixes #2
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.