Skip to content

ng update @angular/cli only works with --from=6.0.7 for 6.0.7 -> 6.0.8 update #11291

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
dominikg opened this issue Jun 18, 2018 · 6 comments
Closed
Assignees
Labels
area: @schematics/angular freq1: low Only reported by a handful of users who observe it rarely needs: repro steps We cannot reproduce the issue with the information given severity3: broken

Comments

@dominikg
Copy link

Bug Report or Feature Request (mark with an x)

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

Area

- [ ] devkit
- [x] schematics

Versions

Angular CLI: local 6.0.7, global 6.0.8
Node: 10.4.1
OS: darwin x64
Angular: 6.0.5

Repro steps

check which packages are available

ng update
    We analyzed your package.json, there are some packages to update:
    
      Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @angular/cli                       6.0.7 -> 6.0.8           ng update @angular/cli
    
    
    There might be additional packages that are outdated.
    Or run ng update --all to try to update all at the same time.

run update command as printed above

ng update @angular/cli
            Found a modern configuration file. Nothing to be done.

Nothing happened

Workaround

explicitly specify the version you are coming from

ng update @angular/cli --from=6.0.7

Desired functionality

either print command with --from or make it work without --from

@Brocco Brocco added freq1: low Only reported by a handful of users who observe it rarely severity3: broken labels Jun 21, 2018
@hansl
Copy link
Contributor

hansl commented Jul 25, 2018

Hi @dominikg ,

I cannot reproduce this on my machine. From a new project:

image

Could you provide a project example so we can clone and have a starting point to investigate? Thanks.

@hansl hansl self-assigned this Jul 25, 2018
@hansl hansl added the needs: repro steps We cannot reproduce the issue with the information given label Jul 25, 2018
@dominikg
Copy link
Author

global versions:

Angular CLI: 6.0.8
Node: 10.6.0
OS: darwin x64

repro script:

# use [email protected] to create new project
npx -p @angular/[email protected] ng new updateme

cd updateme

# new created the project with [email protected] installed locally (due to ^6.0.7 in package.json) so downgrade local cli to 6.0.7
npm install -D @angular/[email protected]

# now try to update to 6.0.8
ng update @angular/cli

@hansl
Copy link
Contributor

hansl commented Jul 25, 2018

Cannot reproduce. Log:

🏢  nvm install 10.6
Downloading https://nodejs.org/dist/v10.6.0/node-v10.6.0-darwin-x64.tar.gz...
######################################################################## 100.0%
Now using node v10.6.0 (npm v6.1.0)
hansl at pro.mtv in ~/Sources/temp, last command was ☀  in 6871ms, time is ⏰ 11:18
🏢  npx -p @angular/[email protected] ng new updateme
CREATE updateme/README.md (1025 bytes)
CREATE updateme/angular.json (3566 bytes)
CREATE updateme/package.json (1312 bytes)
CREATE updateme/tsconfig.json (384 bytes)
CREATE updateme/tslint.json (2805 bytes)
CREATE updateme/.editorconfig (245 bytes)
CREATE updateme/.gitignore (503 bytes)
CREATE updateme/src/environments/environment.prod.ts (51 bytes)
CREATE updateme/src/environments/environment.ts (631 bytes)
CREATE updateme/src/favicon.ico (5430 bytes)
CREATE updateme/src/index.html (295 bytes)
CREATE updateme/src/main.ts (370 bytes)
CREATE updateme/src/polyfills.ts (3194 bytes)
CREATE updateme/src/test.ts (642 bytes)
CREATE updateme/src/assets/.gitkeep (0 bytes)
CREATE updateme/src/styles.css (80 bytes)
CREATE updateme/src/browserslist (375 bytes)
CREATE updateme/src/karma.conf.js (964 bytes)
CREATE updateme/src/tsconfig.app.json (194 bytes)
CREATE updateme/src/tsconfig.spec.json (282 bytes)
CREATE updateme/src/tslint.json (314 bytes)
CREATE updateme/src/app/app.module.ts (314 bytes)
CREATE updateme/src/app/app.component.css (0 bytes)
CREATE updateme/src/app/app.component.html (1141 bytes)
CREATE updateme/src/app/app.component.spec.ts (991 bytes)
CREATE updateme/src/app/app.component.ts (207 bytes)
CREATE updateme/e2e/protractor.conf.js (752 bytes)
CREATE updateme/e2e/src/app.e2e-spec.ts (304 bytes)
CREATE updateme/e2e/src/app.po.ts (208 bytes)
CREATE updateme/e2e/tsconfig.e2e.json (213 bytes)
npm WARN deprecated [email protected]: 1.2.0 should have been a major version bump

> [email protected] install /Users/hansl/Sources/temp/updateme/node_modules/fsevents
> node install

[fsevents] Success: "/Users/hansl/Sources/temp/updateme/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

> [email protected] install /Users/hansl/Sources/temp/updateme/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/hansl/.npm/node-sass/4.9.2/darwin-x64-64_binding.node

> [email protected] postinstall /Users/hansl/Sources/temp/updateme/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/hansl/Sources/temp/updateme/node_modules/node-sass/vendor/darwin-x64-64/binding.node
Testing binary
Binary is fine

> @angular/[email protected] postinstall /Users/hansl/Sources/temp/updateme/node_modules/@angular/cli
> node ./bin/ng-update-message.js

added 1168 packages from 1290 contributors and audited 21755 packages in 49.001s
found 13 vulnerabilities (9 low, 4 high)
  run `npm audit fix` to fix them, or `npm audit` for details
    Successfully initialized git.
hansl at pro.mtv in ~/Sources/temp, last command was ☀  in 63460ms, time is ⏰ 11:20
🏢  cd updateme
hansl at pro.mtv in ~/Sources/temp/updateme on master ✓, last command was ☀  in 16ms, time is ⏰ 11:21
🏢  npm install -D @angular/[email protected]

> @angular/[email protected] postinstall /Users/hansl/Sources/temp/updateme/node_modules/@angular/cli
> node ./bin/ng-update-message.js

+ @angular/[email protected]
added 5 packages from 1 contributor, updated 4 packages and audited 21755 packages in 8.019s
found 13 vulnerabilities (9 low, 4 high)
  run `npm audit fix` to fix them, or `npm audit` for details
hansl at pro.mtv in ~/Sources/temp/updateme on master ✭, last command was ☀  in 8584ms, time is ⏰ 11:21
🏢  ng update @angular/cli
zsh: command not found: ng
hansl at pro.mtv in ~/Sources/temp/updateme on master ✭, last command was 💀 [127] in 18ms, time is ⏰ 11:22
🏢  ./node_modules/.bin/ng update @angular/cli
    Updating package.json with dependency @angular/cli @ "6.0.8" (was "6.0.7")...
UPDATE package.json (1312 bytes)

> @angular/[email protected] postinstall /Users/hansl/Sources/temp/updateme/node_modules/@angular/cli
> node ./bin/ng-update-message.js

removed 5 packages, updated 4 packages and audited 21755 packages in 7.567s
found 13 vulnerabilities (9 low, 4 high)
  run `npm audit fix` to fix them, or `npm audit` for details
hansl at pro.mtv in ~/Sources/temp/updateme on master ✭, last command was ☀  in 10299ms, time is ⏰ 11:22
🏢 

@hansl hansl closed this as completed Jul 25, 2018
@todd-skelton
Copy link

Same issue here for new project

@dominikg
Copy link
Author

@xKloc do you use yarn? this issue may be related #11694

@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 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: @schematics/angular freq1: low Only reported by a handful of users who observe it rarely needs: repro steps We cannot reproduce the issue with the information given severity3: broken
Projects
None yet
Development

No branches or pull requests

5 participants