6rc5 serving without sourcemaps
See original GitHub issueVersions
Angular CLI: 6.0.0-rc.5 (global and local)
Angular: 6.0.0-rc.5
Rxjs 6rc7
webpack 4.5
Repro steps
I can’t ng serve
my app without sourcemap (yes i need disable them in my large project, recompile is too long !
with ng serve
command I tried theses options:
–no-sourcemap
–sourcemap=false
–sourceMap=false
I tried too add in angular.json
serve.configuration production nothing works
Observed behavior
It always serve sourcemap 😦
Desired behavior
Serving without sourcemap
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Using sourcemaps on production without exposing the source ...
Start a static http server to serve generated sourcemaps. Let's take a look how it all works together: This is just an example...
Read more >How to omit sourcemaps in Angular-CLI 6+ - Stack Overflow
Use --source-map . It takes default value true . So following command will not create sourcemaps: ng build --source-map=false.
Read more >Should I Use Source Maps in Production? | CSS-Tricks
Shipping source maps to production is a nice middle ground. There's no hit on performance (source maps don't get loaded unless you have...
Read more >Source Maps - Rollbar Docs
If you generated your source maps without sources, then you need to make sure to follow the 'Uploading a source map with sources...
Read more >Debug Angular apps in production without revealing source ...
Let's start our app and open the dev tools. ng serve. Source maps help us display our original source under webpack:// ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Closing as this appears to be resolved.
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.