Fix sourcemap file resolution for Next.js apps with --next parameter #24
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.
Problem: When using --next parameter to zip sourcemaps, the CLI failed with "ADM-ZIP: File not found" errors for Next.js projects. This occurred because sourcemap URLs like ".next/static/xxx.js.map" were being resolved relative to the JavaScript file's directory instead of the project root.
Solution: Updated extractMapPath() to intelligently resolve sourcemap paths:
This ensures Next.js and other framework sourcemaps are found correctly when creating zip uploads.
Example of the error in commandline:

🤖 Generated with Claude Code
Description of the change
Type of change
Related issues
Checklists
Development
Code review