redis-commander: redis-commander fails to start up
I am on node v0.11.14 with npm v2.0.0. I installed redis-commander but when I try to run it I get
path.existsSync is now called `fs.existsSync`.
/Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/node_modules/browserify/index.js:204
self[key] = w[key].bind(w);
^
TypeError: Cannot read property 'bind' of undefined
at /Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/node_modules/browserify/index.js:204:27
at Array.forEach (native)
at module.exports (/Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/node_modules/browserify/index.js:203:41)
at module.exports (/Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/lib/app.js:48:11)
at startWebApp (/Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/bin/redis-commander.js:158:3)
at /Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/bin/redis-commander.js:116:10
at /Users/gauravarora/.nvm/v0.11.14/lib/node_modules/redis-commander/lib/util.js:135:7
at fs.js:295:14
at Object.oncomplete (fs.js:93:15)
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 37 (8 by maintainers)
Commits related to this issue
- fixes #144 cwd bug The script lib/app.js now sets node's current working directory to the root of the project/repo instead of just inheriting the current tty's cwd so all relative static web assets g... — committed to itsjustcon/redis-commander by itsjustcon 9 years ago
- Merge pull request #155 from itsjustcon/master fixes #144 cwd bug — committed to joeferner/redis-commander by joeferner 9 years ago
- reenable changing cwd on app startup to make browserify work under Windows, refs #144, #182 — committed to sseide/redis-commander by deleted user 6 years ago
I seems like this is still broken in the Docker image?