Provide source maps where available

[silentrob]

Harp should support source maps where available.
http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/

This is landing in Less 1.5
less/less.js#1050

CoffeeScript 1.6
TypeScript supports it

Jade has an issue, but...
pugjs/pug#941

This boils down to generating a second file and referencing it via header.

[sintaxi]

Very cool. Wow, the demand for source maps is pretty crazy.

[kennethormandy]

Stylus has an issues for it too
https://github.com/LearnBoost/stylus/issues/1072

[lfac-pt]

👍

[kebot]

+1

[jesstelford]

Wow, the epicness source maps is pretty awesome.

FTFY ;)

[kebot]

CoffeeScript and Less SourceMap support is added in my fork, will pull-request after my another pull-request is merged.
https://github.com/kebot/terraform/tree/sourcemap

[silentrob]

Holy cow thats rad!

[L8D]

👍 awesome job @kebot

[kebot]

@sintaxi Do you reviewed my pull-request of the support of in memory cache, the source map support is based on it?

[giodamelio]

👍

[KidkArolis]

Is there any progress on this?

[remy]

+1

[amitkeret]

+1

[davej]

Hate to just tack on a +1. I tried Harp and love the simplicity but source maps is the feature which prevents me from switching from Gulp.

[og2t]

Same here. Minification of JS and CSS without source maps doesn't work when you need to debug ;-)

[tjnicolaides]

Just wanted to run this terraform PR past the group to see if I'm on the right path before implementing in the harp project, too.

Once I get into Harp, I'm struggling between the following two choices:

1. Should sourcemaps be ON or OFF by default, with a config option to toggle? Or, if they're available for a particular file extension, are they always ON?
2. Should users have a config option to change which directory maps get written to, with the default being the same directory as the minified CSS/JS? Or are should they always be written to the same directory?

Once we have the .scss maps proofed out, would we finish adding .less/.styl maps to terraform.git, or all available sourcemapped extensions, or just roll out the one for harp.git?

[kennethormandy]

@sintaxi will have the final word on this, but my expectation would be:

1. On by default for all preprocessors (regular HTML, CSS, and JS goes through a different codepath right now) in development environments (ex. harp server) but not in production environments (ex. harp compile, or when using Harp as middleware)
2. Source maps should be served and updated on each request, but not written to the file system every time, which is how the preprocessors already work.

Our goal would be to have them for all preprocessors, but we wouldn’t be opposed to starting with Sass and tagging a release of Terraform, if that was significantly easier.

[davej]

By the way, I ended up writing my own middleware that compiles the usual suspects (sass, less, stylus, coffeescript, babel, etc..) and does sourcemaps too: https://github.com/davej/piggy-in-the-middle

[tjnicolaides]

Ok Harp team, please have a look at the sourcemap pull requests I've opened in Harp and Terraform and advise on how you'd like to see them improved in order to be accepted. Our dev team makes heavy use of Harp and we're really looking forward to making use of *.scss sourcemaps in 2016. Thanks!

[peterwilli]

This is a bit of a bummer :( I just really fell in love with Harp when I found out that my coffeescripts doesn't have source maps mapped to their minified JS counterparts :(

[og2t]

+1