Fix `test:typescript` script for Windows compatibility
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js, typescript
- Domain
- build-system, testing
Research direction
Start by locating the package.json script behind test:typescript and inspect how it passes ./types/*.d.ts to tsc; the issue shows that Windows fails to expand this glob. Run npm run test:typescript on Windows to reproduce the failure, then verify the script succeeds there without changing the intended type checks.
Written by the indexing model from the issue text.
Description
Failing in Windows
PS C:\Users\shivams\Desktop\open-source\undici> npm run test:typescript
npm notice run [email protected] test:typescript
npm notice run tsd && tsc test/imports/undici-import.ts --typeRoots ./types --noEmit && tsc ./types/*.d.ts --noEmit --typeRoots ./types
error TS6053: File './types/*.d.ts' not found.
The file is in the program because:
Root file specified for compilation
Found 1 error.
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 920
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 99
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from nodejs/undici
-
Socks5ProxyAgent: SOCKS5 handshake/auth timeout leaks the underlying socketPossibly taken @drewmt claimed this 53 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
DispatchOptions.upgrade accepts boolean in types but runtime rejects itPossibly taken @mcollina claimed this 102 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Default fetch timeout too shortMay be free again A pull request for this issue was closed without being merged. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nodejs/undici#1373 · 20 comments · 15 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 3/100
nodejs/undici#5989 · 4 comments ·
Maintainers usually reply within 1 day
-
A `Request` reads one chunk of an async-iterable body before anyone reads it (since 8.11.0), which stalls Node's keep-alive sockets under Next.jsPossibly taken @Kesavamoorthig06 claimed this 3 days ago. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
nodejs/undici#5988 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
[Bug] Dev image build fails: `npm install` in the root Dockerfile runs out of memory (exit 134)Possibly taken @andest01 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
good first issue hacktoberfest help wanted
Difficulty 2/5 Under an hour Newbie friendliness 76/100
pacocartones/free-llm-api-hub#262 ·
Maintainers usually reply within 1 day
-
agent-task risk:low
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
guyellis/http-status-check#512 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/playwright#43327 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/TypeScript#64758 ·
Maintainers usually reply within 1 day