Add option for hidden-source-map to use with ng build --prod

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

1.4.0-rc2

Repro steps.

Feature

The log given by the failure.

Feature

Desired functionality.

Add an option to generate hidden source maps for production builds. Hidden source maps are helpful because they are full source maps, but not referenced in the minified files. This allows a developer to use the source maps for debugging purposes without letting the browser know they exist. Error tracking sites such as Atatus allow users to upload source maps manually so the stack traces are more useful and the maps never need to be made public.

In my case, I have modified my fork of the cli to generate hidden source maps when using the production build and source-maps=true. This has worked for me, but I didn’t expect it would be the best fit for the whole project.

devtool: buildOptions.sourcemaps ? 'hidden-source-map' : false,

https://github.com/mhamel06/angular-cli/blob/2f551150bccdeb6121c79f0b1fd65bfdd68c33ce/packages/%40angular/cli/models/webpack-configs/production.ts#L108-L110

Mention any other details that might be useful.

https://webpack.js.org/configuration/devtool/

[matt-senseye]

@cburger - if it’s helpful, as a workaround what we do is have a script in package.json which runs ng build then immediately moves the sourcemaps out of dist and into a separate sourcemaps folder. This allows us to upload them to Sentry without including them in the app deployment. It’d be better if they were proper hidden sourcemaps, but it gets us most of the way there.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}