Last modified: 2013-12-02 22:15:14 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59689, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57689 - Lacking dependencies in parsoid package.json
Lacking dependencies in parsoid package.json
Status: RESOLVED INVALID
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized trivial
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-27 23:26 UTC by Kelson [Emmanuel Engelhart]
Modified: 2013-12-02 22:15 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kelson [Emmanuel Engelhart] 2013-11-27 23:26:51 UTC
"qs" and "connect" are mandatory dependencies but not listed in package.json.

Here is the error with "npm install; nodejs api/server.js"
module.js:340
    throw err;
          ^
Error: Cannot find module 'connect'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/var/www/devwiki/w/parsoid/js/node_modules/express/lib/express.js:12:15)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
worker 20858 died (8), restarting.
Comment 1 ssastry 2013-12-02 21:12:08 UTC
That is odd. They are not direct dependencies. qs comes in through request, and connect via express. request and express should have installed them.
Comment 2 Kelson [Emmanuel Engelhart] 2013-12-02 22:15:14 UTC
I have re-investigate this in details, it seems I have had some permissions problems which were not stopping the node module installation... Now it works.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links