Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a way to specify which source maps to create with production build? #2533

Closed
billdwhite opened this issue Oct 5, 2016 · 11 comments
Closed

Comments

@billdwhite
Copy link

Since there is no access to the webpack.config.js (and it's devtool setting) for angular-cli, is there any way to control which type of sourcemaps are generated in the production build? I want the production build and compression, etc but I want usable TS sources as well so I can troubleshoot the code once it is deployed. This that possible?

@filipesilva
Copy link
Contributor

I think #2519 fixes this.

@billdwhite
Copy link
Author

billdwhite commented Oct 10, 2016

@filipesilva I see this is waiting for a sync ("This branch is out-of-date with the base branch"). Any ETA on that?

@tomwanzek
Copy link

@filipesilva Just to clarify, are TS sourcemaps for prod build always enabled now? Or is there a build time command option to control whether source maps are created? Thx, in advance for a brief reply.

@billdwhite
Copy link
Author

@filipesilva thanks!!

JJayet pushed a commit to JJayet/angular-cli that referenced this issue Oct 14, 2016
@filipesilva
Copy link
Contributor

@tomwanzek always. That was the original intention but we forgot to correctly configure UglifyJsPlugin.

Brocco pushed a commit that referenced this issue Oct 19, 2016
@maxailloud
Copy link

@filipesilva And if we don't want map files in prod is it possible to not have them?
Because if I want to deploy my website having a map file of like 10Mo is a bit too heavy, and as I don't need them. I would need them but not for my prod build, so maybe a parameter to configure it can be good.
Just tell me if it's possible/planned or not and I will deal with it.

texel pushed a commit to splice/angular-cli that referenced this issue Nov 3, 2016
@filipesilva
Copy link
Contributor

@maxailloud not something that's specifically planned atm. Although to be honest there have been a fair number of these requests to further customise minor aspects of builds, so probably in the future we'll just have way more flags there.

For now though, I wouldn't expect it soon as there are way bigger fish to fry. In your specific case I'd make the file copy script ignore/delete the map files when deploying, there should be no problem.

@maxailloud
Copy link

@filipesilva Yeah sure I can definitley understand that there is more important stuff to do.
Yeah i will just delete the map file.

Thank you for your answer.

@Avien
Copy link

Avien commented Nov 10, 2016

I also need an option to build without source maps, seems basic

@filipesilva
Copy link
Contributor

Fixed by #3113

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants