Skip to content

1.5.0-rc.4 release broken #8202

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
brandom opened this issue Oct 26, 2017 · 4 comments · Fixed by #8204
Closed

1.5.0-rc.4 release broken #8202

brandom opened this issue Oct 26, 2017 · 4 comments · Fixed by #8204

Comments

@brandom
Copy link

brandom commented Oct 26, 2017

Bug Report or Feature Request (mark with an x)

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

Versions.

Angular CLI: 1.5.0-rc.4
Node: 8.8.0
OS: darwin x64

Repro steps.

npm i -g @angular/cli@1.5.0-rc.4
ng --version

The log given by the failure.

/path/@angular/cli/upgrade/version.js:12
const { bold, red, yellow } = chalk_1.default;
        ^

TypeError: Cannot destructure property `bold` of 'undefined' or 'null'.
    at Object.<anonymous> (/path/@angular/cli/upgrade/version.js:12:39)
    at Module._compile (module.js:612:30)
    at Object.Module._extensions..js (module.js:623:10)
    at Module.load (module.js:531:32)
    at tryModuleLoad (module.js:494:12)
    at Function.Module._load (module.js:486:3)
    at Module.require (module.js:556:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/path/@angular/cli/commands/build.js:4:19)
    at Module._compile (module.js:612:30)

Desired functionality.

Output version.

Mention any other details that might be useful.

Same error generated for all cli commands. ng --version works outside of CLI project.

@hansl
Copy link
Contributor

hansl commented Oct 26, 2017

hey @brandom

Could you try nuking your node_modules and reinstalling? See if that helps.

Also, could you do npm ls chalk and npm ls -g chalk to help us? thanks!

filipesilva added a commit to filipesilva/angular-cli that referenced this issue Oct 26, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Oct 26, 2017
hansl pushed a commit that referenced this issue Oct 26, 2017
@leocaseiro
Copy link

I've fixed installing chalk

npm install chalk@latest --save-dev

Thanks guys!

hansl pushed a commit that referenced this issue Oct 27, 2017
@intellix
Copy link
Contributor

had this myself after an npm i @angular/cli@next but fixed it after deleting package-lock.json and reinstalling. My lock was depending on chalk 2.1.0 but afterwards it was 2.3.0 and worked

asnowwolf pushed a commit to asnowwolf/angular-cli that referenced this issue Nov 2, 2017
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this issue Apr 23, 2018
@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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants