Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
Heroku + parse-server 2.2.4 + parse-dashboard 1.0.7
"parse-dashboard": "1.0.7" to package.jsonvar parseDashboard = require('parse-dashboard'); to the top of index.js2016-04-04T21:53:11.954272+00:00 heroku[web.1]: Starting process with command `node index.js`
2016-04-04T21:53:14.655732+00:00 app[web.1]: module.js:338
2016-04-04T21:53:14.655749+00:00 app[web.1]: throw err;
2016-04-04T21:53:14.655750+00:00 app[web.1]: ^
2016-04-04T21:53:14.655759+00:00 app[web.1]: Error: Cannot find module 'parse-dashboard'
2016-04-04T21:53:14.655767+00:00 app[web.1]: at Function.Module._resolveFilename (module.js:336:15)
2016-04-04T21:53:14.655768+00:00 app[web.1]: at Function.Module._load (module.js:278:25)
2016-04-04T21:53:14.655768+00:00 app[web.1]: at Module.require (module.js:365:17)
2016-04-04T21:53:14.655769+00:00 app[web.1]: at require (module.js:384:17)
2016-04-04T21:53:14.655769+00:00 app[web.1]: at Object.<anonymous> (/app/index.js:3:22)
2016-04-04T21:53:14.655770+00:00 app[web.1]: at Module._compile (module.js:460:26)
2016-04-04T21:53:14.655770+00:00 app[web.1]: at Object.Module._extensions..js (module.js:478:10)
2016-04-04T21:53:14.655771+00:00 app[web.1]: at Module.load (module.js:355:32)
2016-04-04T21:53:14.655771+00:00 app[web.1]: at Function.Module._load (module.js:310:12)
2016-04-04T21:53:14.655772+00:00 app[web.1]: at Function.Module.runMain (module.js:501:10)
2016-04-04T21:53:15.577557+00:00 heroku[web.1]: Process exited with status 1
2016-04-04T21:53:15.601834+00:00 heroku[web.1]: State changed from starting to crashed
I've searched around a lot and it seems like this was an issue that was previously fixed. I feel like I'm probably doing something wrong.
Does it work locally?
Same error
did you run npm install after adding to the package.json ?
I think this fix hasn't been published on npm yet. It will be part of 1.0.8. For now, I'd suggest using following the suggestions in the readme (install globally and using the command line)
I was actually checking that, what @drew-gross said !
I did run NPM install.
That makes sense! Do you have an estimated release date?
Thanks!
It should be sometime this week.
1.0.8 is on npm now. Please try that and reopen if you still have issues.
It works, thanks!
Most helpful comment
did you run npm install after adding to the package.json ?