Sourcemap support?

Open
#37 12 comments 7 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
build-system

Research direction

Review the plugin's stream behavior alongside gulp-sourcemaps to determine where sourcemap accuracy is lost. The issue names no files or tests; done would mean establishing whether support is possible and confirming accurate sourcemaps when the plugin is used in the stream.

Written by the indexing model from the issue text.

Description

Should this plugin work with gulp-sourcemaps?

I'm asking because in my case it doesn't seem to --- the addition of this plugin into my stream makes the sourcemaps inaccurate.

I see no mention of "sourcemap" in the repo; so before I dug deeper I just wanted to check: Has any effort already been made to support sourcemaps with this plugin? Maybe I am missing something?

Dominant language
JavaScript
Stars
495
Forks
87
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 lazd/gulp-replace

All issues in lazd/gulp-replace

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.