[BUG] windows: file not found: syntaxes/*.ym (code ELIFECYCLE)
Open
Nobody has claimed this yet.
Bug
Needs Triage
Release 9.x
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
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 have a npm script that invokes a dependency with a glob pattern: "myscript": "yaml2json \"syntaxes/*.yml\"".
On Linux the pattern resolves just fine, but on Windows it won't work.
Expected Behavior
Convert all .yml files in the given directory without error.
Steps To Reproduce
- Windows 10, https://github.com/serkonda7/vscode-vba
- See below
- Run
npm run convert-yaml - See error...
Environment
- npm: 9.0.1
- Node.js: 18.12.0
- OS Name: Windows 10
- System Model Name: Dell E5410
- npm config:
; "builtin" config from C:\Users\redacted\AppData\Roaming\npm\node_modules\npm\npmrc
prefix = "C:\\Users\\redacted\\AppData\\Roaming\\npm"
; node bin location = C:\Program Files\nodejs\node.exe
; node version = v18.12.0
; npm local prefix = C:\redacted\vscode-vba
; npm version = 9.0.1
; cwd = C:\redacted\vscode-vba
; HOME = C:\Users\redacted
; Run `npm config ls -l` to show all defaults.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the npm script on Windows 10 using the linked vscode-vba example, then compare its handling of yaml2json "syntaxes/*.yml" with Linux behavior. Trace the npm CLI path that launches dependency scripts and verify the result by converting all .yml files without a file-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100