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.

Sign up for GitHub

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

Jump to bottom

npm v8.13.1 文件名、目录名或卷标语法不正确。 #5075

Closed
2 tasks done
shunyue1320 opened this issue Jun 24, 2022 · 2 comments
Closed
2 tasks done

npm v8.13.1 文件名、目录名或卷标语法不正确。 #5075

shunyue1320 opened this issue Jun 24, 2022 · 2 comments
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

@shunyue1320
Copy link

shunyue1320 commented Jun 24, 2022 •
edited

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

C:\Users\admin\working\F2E-harbour-web>npm run server:local

truckharbour@1.0.0 server:local
rimraf dist && npm run fix-memory-limit && webpack-dev-server --config webpack.local.js --progress --profile --watch --content-base ./dist --inline

文件名、目录名或卷标语法不正确。

Expected Behavior

No response

Steps To Reproduce

  1. npm run ...
  2. 文件名、目录名或卷标语法不正确。

Environment

  • npm: v8.13.1
  • Node.js: v16.12.0
  • OS Name: windows 11
  • System Model Name: windows
  • npm config: npm run ...
; copy and paste output from `npm config ls` here
@shunyue1320 shunyue1320 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 24, 2022
@JonasSchubert
Copy link

Related to #5066

peterjuras added a commit to coat-dev/coat that referenced this issue Jun 25, 2022
@peterjuras
ci: 👷 temp: Fix npm version for e2e tests to v8.12
cbf1ff6 
npm v8.13 breaks running lifecycle scripts that contain a colon. See npm/cli#5075
@fritzy
Copy link
Contributor

fritzy commented Jun 28, 2022

This is a dupe and a fix is in place for the next release.

@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
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fritzy @JonasSchubert @shunyue1320