Does not work on iOS with terminal emulation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 474
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 53
Description
Describe the bug
Netlify CLI installed with npm install -g netlify-cli but netlify command returns "command not found". Happens on iPhone using iSH app (Alpine Linux), where Node/npm install but global binaries not in PATH. Also occurs on occasional computers after global install – netlify login or netlify deploy fail with same error.
Typical errors: "netlify: command not found", EACCES permissions during global install, or iSH too slow/unresponsive for practical use. Goal is to deploy static/simple projects via CLI from terminal, but it doesn't work.
Steps to reproduce
No netlify.toml present because netlify init cannot be run successfully.
Example for basic static/SPA project if it worked:
[build]
publish = "build"
command = "npm run build" # or empty for pure static
[[redirects]]
from = "/*"
to = "/index.html"
status = 200
Configuration
No netlify.toml present because netlify init cannot be run successfully.
Example for basic static/SPA project if it worked:
[build]
publish = "build"
command = "npm run build" # or empty for pure static
[[redirects]]
from = "/*"
to = "/index.html"
status = 200
Environment
Cannot run full npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli due to iPhone limitation (no stable full terminal; iSH PATH/global bins broken after install).
Partial info:
- OS: iOS / iPhone with iSH (Alpine Linux emulated)
- Node: v20+ (via apk add nodejs)
- npm: recent version
- netlify-cli: installed globally (~23.x), but not executable ("command not found")
- PATH issue: global npm bins not in shell PATH in iSH
Will add full envinfo output from computer if possible later.
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
No repository file, test, or entry point is identified in the report. Start by reproducing the global installation and PATH behavior on iSH and an affected computer, then determine a project-level change that addresses the reported command-not-found and permissions cases; done means the documented installation works or the unsupported environment is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, node.js, typescript
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100