Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Quick Start error

See original GitHub issue

Hi, I was trying to follow the quick-start guide.

I got the following error:

> npm start

> decide@0.0.1 start /home/quang/dev/decide
> hoodie


/home/quang/dev/decide/node_modules/hoodie/bin/start.js:9
    throw error
    ^
OpenError: IO error: .hoodie/data/hoodie-config/LOCK: No such file or directory
    at /home/quang/dev/decide/node_modules/hoodie/node_modules/pouchdb-adapter-leveldb/node_modules/levelup/lib/levelup.js:119:34
    at /home/quang/dev/decide/node_modules/hoodie/node_modules/pouchdb-adapter-leveldb/node_modules/leveldown/node_modules/abstract-leveldown/abstract-leveldown.js:39:16

npm ERR! Linux 3.16.0-4-amd64
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code ELIFECYCLE
npm ERR! decide@0.0.1 start: `hoodie`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the decide@0.0.1 start script 'hoodie'.
npm ERR! This is most likely a problem with the decide package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     hoodie
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs decide
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! 
npm ERR!     npm owner ls decide
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/quang/dev/decide/npm-debug.log

I’m using node version v4.4.7

my package.json is https://github.com/quangv/decide/blob/master/package.json

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

gr2mcommented, Jan 8, 2017

Great, thanks for letting us know!

For reference, here is a description of the bug causing the problem you run into: https://github.com/hoodiehq/hoodie-server/issues/529. If you like, I’d be happy to help you land a fix for it? No worries if not, I’m sure we get this resolved soon.

Thanks again for reporting it!

0reactions

gr2mcommented, Apr 11, 2017

thanks for letting us knwo @kevinkhuat 👍

I think this issue has been resolved meanwhile, thanks!