Activity

1. alan-agius4 commented on Jan 23, 2019

   

   alan-agius4

   on Jan 23, 2019

   Last edited by alan-agius4

   Collaborator

   More actions

   Hi,

   What is the usecase of not deploying the sourcemaps?

   If it’s for reporting purposes I suggest you use the ‘hidden` sourcemap which have been added recently see here #13062
2. alan-agius4

   added

   needs: more infoReporter must clarify the issueReporter must clarify the issue

   on Jan 23, 2019
3. alan-agius4 commented on Jan 29, 2019

   

   alan-agius4

   on Jan 29, 2019

   Collaborator

   More actions

   Thanks for reporting this issue

   Closing as hidden, should be enough. If you have another use case. Kindly open a new issue explaining why you cannot use hidden.

   Thanks.
4. alan-agius4

   closed this as completedon Jan 29, 2019
5. johnhamm commented on Aug 15, 2019

   

   johnhamm

   on Aug 15, 2019

   More actions

   A use case would be using "hidden" sourcemaps on a production deployment. You would name the subfolder under dist something secret, then add the sourcemaps when you want to debug the production deploy using that URL subdirectory.
6. alan-agius4 commented on Aug 16, 2019

   

   alan-agius4

   on Aug 16, 2019

   Collaborator

   More actions

   Hi @johnhamm, why would you want to deploy your sourcemaps in a 'secret' folder instead of using the hidden sourcemaps feature within the CLI, and when you want to debug you just add the sourcemap from Google Chrome using the Add source map feature?.

   There is quite a good article about this in https://blog.angularindepth.com/debug-angular-apps-in-production-without-revealing-source-maps-ab4a235edd85
7. johnhamm commented on Aug 16, 2019

   

   johnhamm

   on Aug 16, 2019

   More actions

   The article you linked to explains why:

   Uploading source maps from your local machine is quite nice. But still, it requires some manual steps that each developer has to execute. Finding the matching commit, regenerate source maps and upload them. Can we get rid of some of them?

   Again we start off by setting the hidden property in our angular.json.
   "sourceMap": {
   "hidden": true,
   "scripts": true,
   "styles": true
   }
   Next up we need to hide our source maps. We merely create another folder in our dist and move the source maps to it.
   "postbuild": "mkdir dist/sourceMapInspector/sourceMaps; mv dist/sourceMapInspector/*.map dist/sourceMapInspector/sourceMaps"
   You are free to choose the directory name. Instead of sourceMaps you can also choose some name that is hard or impossible to guess.

   You'd still use the hidden feature, but you'd move the source maps to a subfolder which you would publish along with the website into a subdirectory name.

   The advantages are obvious - the developer doesn't have to find the matching commit, generate the sourcemaps, and upload them. Instead, they can merely add them using the subdirectory from whatever deploy they are accessing.
8. clydin commented on Aug 17, 2019

   

   clydin

   on Aug 17, 2019

   Member

   More actions

   There's no need to move them. Instead, just don't deploy the source map files.
9. angular-automatic-lock-bot commented on Sep 17, 2019

   

   angular-automatic-lock-botbot

   on Sep 17, 2019

   More actions

   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.}
10. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Sep 17, 2019