Add sourcemap generation to build process #217
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.
The process isn't brilliant - for some reason, when the maps pass through both babel and uglify, the line numbers seem to get a bit screwy. Each transform on its own works absolutely fine. That said, I figured that for most people, it would be preferably to have the original source, rather than super-precise line numbers. Besides, once you actually get into the meat of the code, the line numbers match up again, it's just the initialisation at the very start of the file that seems to not work so well.
The alternative would be to remove the
{loadMaps: true}
option on line 18 of the gulpfile. This would mean thatdist/angular-vs-repeat.js
would map to the original file, butdist/angular-vs-repeat.min.js
would only map todist/angular-vs-repeat.js
(i.e. only display the changes of minification, not the original Babel transforms).I also removed the gulp-clean dependency and import, because it wasn't used at all.
(Sourcemap demo: here.)