Skip to content

leave file in output directory when build fail #7501

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

Closed
zh99998 opened this issue Aug 25, 2017 · 3 comments
Closed

leave file in output directory when build fail #7501

zh99998 opened this issue Aug 25, 2017 · 3 comments
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient

Comments

@zh99998
Copy link

zh99998 commented Aug 25, 2017

Bug Report or Feature Request (mark with an x)

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

Desired functionality.

I got a error in build time

ERROR in main.5ab8f909c72c397a5791.bundle.js from UglifyJs
Unexpected token: punc (}) [main.5ab8f909c72c397a5791.bundle.js:217,0]

well...this is hard to debug, no detail, no file, I can't know what happens.
seems there is a npm module using es6 syntax and uglifyjs, but don't know which module do that.

request add a feature to keep output files when build fail.

@Brocco Brocco added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient labels Aug 29, 2017
@filipesilva
Copy link
Contributor

I agree it's confusing, but truth is that on uglify errors like this one there never is a file on disk to leave, it's all in memory.

@filipesilva
Copy link
Contributor

Ah, here is the original issue for this problem and the real answer: #5741 (comment)

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient
Projects
None yet
Development

No branches or pull requests

3 participants