[V3] make install scripts
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24.6k
- Forks
- 941
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 24
Description
Feature parity
| Platform \ Feature | Daemon | PATH | Location |
|---|---|---|---|
| Windows | ❌ | ✅ | install.ps1 |
| MacOS | ❌ | ✅ | build/darwin/scripts/postinstall |
| Linux | N/A | N/A | N/A |
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
Start by comparing install.ps1 with build/darwin/scripts/postinstall and checking how the CLI installation flow handles PATH, location, and daemon setup on each platform. Use the feature-parity table as the completion checklist; done means the Windows and macOS installation scripts cover the listed supported features consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100