Description
I was running an older and apparently unsupported version of node and found that ix map failed with no indication of the problem. It worked fine after switching to a newer version.
I didn't see a minimum node version listed anywhere. I totally get why you wouldn't want to support older versions of node, but "Fetch failed" is hard to reason about.
Steps to reproduce
- Run
ix map . using an older version of node (I used v18.20.7, but I didn't check any others)
Expected behavior
I expected it to work, but an actionable error message would have been enough.
Actual behavior
A mysterious "Fetch failed" message.
CLI output
$ ix map .
[ok] Backend is already running and healthy
Memory Layer: http://localhost:8090
ArangoDB: http://localhost:8529
Ingested in 90.0s
Error: fetch failed
Environment
- OS: Linux
- Node: v18.20.7
- Ix version: 0.5.1
Description
I was running an older and apparently unsupported version of node and found that
ix mapfailed with no indication of the problem. It worked fine after switching to a newer version.I didn't see a minimum node version listed anywhere. I totally get why you wouldn't want to support older versions of node, but "Fetch failed" is hard to reason about.
Steps to reproduce
ix map .using an older version of node (I used v18.20.7, but I didn't check any others)Expected behavior
I expected it to work, but an actionable error message would have been enough.
Actual behavior
A mysterious "Fetch failed" message.
CLI output
Environment