Option to output absolute paths for source maps?

Open
#387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript

Research direction

Start by tracing how ncc generates source maps and turns original source paths into relative paths. Reproduce the behavior described for now dev, then identify the existing option and output boundaries that would need to support absolute paths. Done means the option produces absolute original-source paths without changing the default behavior.

Written by the indexing model from the issue text.

Description

enhancement

Would it be possible to add an option to make the source maps output an absolute path rather than a relative path? This would be useful for now dev to show the original source file paths rather than the path where the lambda is being executed.

Dominant language
JavaScript
Stars
9.8k
Forks
326
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/ncc

All issues in vercel/ncc

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.