You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I figured it out. Here you state that [email protected] is currently assumed to be installed globally but in the dependencies list, you put [email protected]. I guess that wasn't a good assumption cuz I've never done anything with browserfs before and once I changed the dependency value to the 2.0.0 version, the error didn't show up on npm start
Is there a reason for the discrepancy? If not I will do a fork.
I had patched [email protected], which is why I didn't want to upgrade, but I still needed the make_http_index CLI only available in [email protected]. That's how I came to depend on two separate versions of the same package.
I've now documented this on the readme, and I'm working on migrating to ZenFS, a fork of BrowserFS.
I guess I could have also used package aliases to avoid needing a global install, since I only needed the command from one of the versions, and the other version didn't have the command. That's assuming npm 6.9.0 was out at the time.
I'm getting an npm error when I do
npm start
make_http_index | json > filesystem-index.json sh: make_http_index: command not found
Is this an NPM error?
The text was updated successfully, but these errors were encountered: