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

[BUG] npm 8.13.1 error when using --ssl: The filename, directory name, or volume label syntax is incorrect. #5092

Closed
2 tasks done
pawan-gwebs opened this issue Jun 28, 2022 · 1 comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release

Comments

@pawan-gwebs
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

I'm stuck with this error
I used command: "npm start", which is using " run-script-os" to serve ng application

appx@0.0.0 start
run-script-os

npm WARN config global --global, --local are deprecated. Use --location=global instead.

appx@0.0.0 start:windows
ng serve --ssl --ssl-cert %APPDATA%\ASP.NET\https%npm_package_name%.pem --ssl-key %APPDATA%\ASP.NET\https%npm_package_name%.key

The filename, directory name, or volume label syntax is incorrect.

Expected Behavior

App should be run/compile successfully.

Steps To Reproduce

No response

Environment

  • npm: v8.13.1
  • Node.js: v16.15.1
  • OS Name: Windows 10
  • System Model Name:
  • npm config:
; copy and paste output from `npm config ls` here
@pawan-gwebs pawan-gwebs added Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release labels Jun 28, 2022
@fritzy
Copy link
Contributor

fritzy commented Jun 28, 2022

There's a known issue with colons in scriptnames on windows for 8.13.1 that should be fixed in tomorrow's release. #5066

It's confusing that you're getting the --global warning with 8.13.1 as that's been removed.

@fritzy fritzy closed this as completed Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release
Projects
None yet
Development

No branches or pull requests

2 participants