Dont use npm global installs for ceramic

[3benbox]

Startup fails when running wheel quiet generate due to an incorrect path to the ceramic install.

This PR keep all modules local and works fine for me.

If we want to globally install the packages, I think there should be an explicit flag as we're making changes to the system outside the working directory.

[dbcfd]

@3benbox sadly, this doesn't work with the example app. The example app expects ceramic to be installed globally. I'd prefer us not installing globally as well.

[3benbox]

I think this is working for me with the example app.

Just running "wheel" and keeping the default config completes successfully and I'm able to access the app on http://localhost:3000 with these changes.

Is there some other issue?

[dav1do]

Ah, I didn't notice this PR.. but I also did the same thing in #26 as the new version of the example app brings its own versions of node_modules now and runs them via scripts.

[3benbox]

Ah, I didn't notice this PR.. but I also did the same thing in #26 as the new version of the example app brings its own versions of node_modules now and runs them via scripts.

Ah, thanks! I'll close this