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

ng update conflict with pc user folder name #17870

Closed
1 of 15 tasks
IR4N0nY opened this issue Jun 5, 2020 · 7 comments · Fixed by #20936
Closed
1 of 15 tasks

ng update conflict with pc user folder name #17870

IR4N0nY opened this issue Jun 5, 2020 · 7 comments · Fixed by #20936

Comments

@IR4N0nY
Copy link

IR4N0nY commented Jun 5, 2020

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • xi18n
  • run
  • config
  • help
  • version
  • doc

Description

unfortunately my pc user name is: s&a and because npm and node have problem with this user name i moved my npm and npm-cache folder to c:\npmGlobal and install node on my D drive and save path to my system variable and edit npmrpc file but when i try to use command ng update i got this error:

PS D:\Projects\Angular\MofidBot\MofidBot\ClientApp> ng update
Your global Angular CLI version (9.1.7) is greater than your local
version (8.3.14). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
The installed Angular CLI version is older than the latest published version.
Installing a temporary version to perform the update.
Installing packages for tooling via npm.
Error: EPERM: operation not permitted, mkdir 'C:\Users\s'
The system cannot find the path specified.
An unhandled exception occurred: Package install failed, see above.
See "C:\Users\s&a\AppData\Local\Temp\ng-lOKcYV\angular-errors.log" for further details.

🌍 Your Environment

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 8.3.14
Node: 14.3.0
OS: win32 x64
Angular: 8.2.12
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router

Package                                    Version
--------------------------------------------------------------------
@angular-devkit/architect                  0.803.24
@angular-devkit/build-angular              0.803.24
@angular-devkit/build-optimizer            0.803.24
@angular-devkit/build-webpack              0.803.24
@angular-devkit/core                       8.3.24
@angular-devkit/schematics                 8.3.14
@angular/cli                               8.3.14
@ngtools/webpack                           8.3.24
@nguniversal/module-map-ngfactory-loader   8.1.1
@schematics/angular                        8.3.14
@schematics/update                         0.803.14
rxjs                                       6.5.4
typescript                                 3.5.3
webpack                                    4.39.2
@Jefiozie
Copy link
Contributor

Hi @alan-agius4, could you point me in the right direction where/ what the problem is. I can have a look at this issue.

@alan-agius4
Copy link
Collaborator

Likely it's caused here

const argv = [binPath, ...args];
const { status, error } = spawnSync('node', argv, {
by unescaped paths.

@Jefiozie
Copy link
Contributor

Just an update, I've not have found the time to research this.

@abadi003
Copy link

is this problem happens with just update or happens with other commands?

@IR4N0nY
Copy link
Author

IR4N0nY commented Feb 24, 2021

update only

@tingwei628
Copy link

tingwei628 commented May 20, 2021

I think node/issue#7367 should be helpful to fix this issue.

@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 Jun 25, 2021
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