Feedback for “Getting started”
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 25
- Forks
- 48
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 7
Description
I tried either windows and WSL and it cannot use napi :
(base) nico@mypc:/mnt/d/$ yarn global add @napi-rs/cli
yarn global v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "@napi-rs/cli@2.18.2" with binaries:
- napi
Done in 0.33s.
(base) nico@mypc:/mnt/d/$ napi
Command 'napi' not found, did you mean:
command 'nap' from snap nap-snippets (0.1.1)
command 'qnapi' from deb qnapi (0.1.9-1build2)
command 'nabi' from deb nabi (1.0.0-4)
See 'snap info ' for additional versions.
Contributor guide
No contributing guide indexed for this repository
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
Start with the “Getting started” page and reproduce the reported Windows and WSL installation commands, including the global @napi-rs/cli install. Trace whether the documented setup makes the napi command available, and consider the issue done when the instructions work or clearly explain the required environment and PATH setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100