Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Is a sourceMapPath/Name option considered? #159

Open
radkodinev opened this issue Aug 20, 2014 · 1 comment
Open

Is a sourceMapPath/Name option considered? #159

radkodinev opened this issue Aug 20, 2014 · 1 comment

Comments

@radkodinev
Copy link
Contributor

Are there any plans for a sourcemapPath option (such as in gulp-ruby-sass), or even better sourceMapName (as in grunt-contrib-uglify)?

I think it would be very useful to be able to control those paths. For instance, in a development environment I would like all the files (script.coffee, script.js, script.js.map) to reside in the same directory.
@radkodinev radkodinev changed the title Is a sourcemapPath option considered? Is a sourcemapPath/Name option considered? Aug 20, 2014
@radkodinev radkodinev changed the title Is a sourcemapPath/Name option considered? Is a sourceMapPath/Name option considered? Aug 20, 2014
@tsov
Copy link

tsov commented Mar 18, 2015

+1 Yes, looking for this option too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsov @radkodinev