Fix double .js extension in build output #25
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the issue where the build was generating
index.js.jsinstead ofindex.js.Changes
fileNamefrom'index.js'to'index'in vite.config.tsentryFileNames: 'index.js'to rollup output options to ensure correct output filenameProblem
The npm package was including
index.js.jsin the dist folder, causing import resolution failures with esbuild and other bundlers.Solution
Vite/Rollup automatically adds the appropriate extension based on the format, so we shouldn't include
.jsin thefileName. TheentryFileNamesoption ensures the final output is exactlyindex.js.Closes #24