-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vite/rollup: Return empty sourcemaps #706
Conversation
🦋 Changeset detectedLatest commit: 64e07de The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
const assetId = emittedFiles.get(importPath)!; | ||
const assetName = this.getFileName(assetId); | ||
const fixedImportPath = `./${normalize( | ||
relative(chunkPath, assetName), | ||
)}`; | ||
return codeResult.replace(importPath, fixedImportPath); | ||
}, code); | ||
return { | ||
code: output, | ||
map: chunkInfo.map ?? null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is null
handled differently than undefined
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it seems so. When I tested it chunkInfo.map
actually was undefined and still resulted in the same warning. But with null
it is suppressed.
Fixes #699
This suppresses the warnings in vite and rollup.
I'm not sure this is really what we want though. Logically this is wrong and the warning actually is correct.