Error running `npm install` on Windows when @stdlib/stdlib is a dependency

[mfantham]

Checklist

Please ensure the following tasks are completed before filing a bug report.

• Read and understood the Code of Conduct.
• Searched for existing issues and pull requests.

Description

Description of the issue.

Encountered an error on Windows when running npm i for the second time in a project which has @stdlib/stdlib as a dependency.

Related Issues

Does this issue have any related issues?

No, I could not find any related issues.

The problem was caused, I believe, by line 282 in this commit

Questions

Any questions for reviewers?

No.

Other

Any other information relevant to this issue? This may include screenshots, references, stack traces, sample output, and/or implementation notes.

Reproduction

What steps are required to reproduce the unexpected output?

In order to reproduce this bug, do the following:

On Windows (tested on Windows 10 Version 2004)

• Create a new npm project with @stdlib/stdlib as a dependency in package.json

mkdir bug-test && cd bug-test && npm init -y
edit package.json
# "dependencies": { "@stdlib/stdlib": "0.0.92"}

• npm install - completes with no errors the first time
• npm install - second time installation throws the error

Expected Results

What are the expected results?

The following results are expected:

• npm should install without an error

Actual Results

What are the actual results?

The following are the actual results:

npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name "@stdlib/array\buffer": name can only contain URL-friendly characters

Environments

What environments are affected (e.g., Node v0.4.x, Chrome, IE 11)? If Node.js, include the npm version, operating system, and any other potentially relevant platform information.

The following environments are affected:

• npm on Windows (tested with npm v6.14.5, node v13.10.1, Windows 10 Version 2004)

[kgryte]

@mfantham Thanks for reporting this and for creating a fix!

[JakenHerman]

Has this fix been published? This is still occuring as of 12/3/2020. If it's on the publish-horizon, are there any temporary workaround solutions you could suggest?

[kgryte]

Sorry for the delay. A new version was published which should address this issue. If not, please reopen this issue.