Reputation: 2429
How to keep sourcemaps after production build?
Right now, my command looks like this:
"build-prod": "ng build --app=release -prod && cp -R lang dist"
I tried changing it to:
ng build --app=release --sourceMap=true -prod && cp -R lang dist
but nothing changed.
If I do:
ng build --sourcemap
I get sourcemaps but then I get index.html instead of index.prod.html.
Is it possible to edit the first command to build sourcemap files?
this is my tsconfig.json
file:
{
"compileOnSave": false,
"compilerOptions": {
"outDir": "./dist/out-tsc",
"sourceMap": true,
"declaration": false,
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"target": "es5",
"typeRoots": [
"node_modules/@types"
],
"lib": [
"es2017",
"dom"
]
}
}
Upvotes: 27
Views: 32013
Reputation: 20132
You should edit your angular.json
like this
"configurations": {
"production": {
"fileReplacements": [
{
"replace": "src/environments/environment.ts",
"with": "src/environments/environment.prod.ts"
}
],
"optimization": true,
"outputHashing": "all",
"sourceMap": false, // change to true
Then run
ng build --prod
But I wouldnt recommend you turn on source map in production because it will increase a bundle size
Upvotes: 37