https://bugzilla.wikimedia.org/show_bug.cgi?id=52840
--- Comment #3 from C. Scott Ananian <canan...@wikimedia.org> --- I think the problem is actually with connect (which provides the bodyParser middleware). We're using connect version 1.9.2, but express only requires connect '1.x'. As far as I can tell from https://github.com/senchalabs/connect/blob/master/History.md, the latest stable 1.x version was 1.8.5, and bodyParser was added/extended in connect 2.0.0. I'm guessing that connect 1.9.2 is a "prerelease 2.0" and so contains some connect 2.0.0 features, like bodyParser. If someone can reproduce this bug, I'd like to see what happens if they edit node_modules/express/package.json to depend on connect 1.9.x instead of 1.x, and then npm install from the node_modules/express directory. Alternatively, we might suggest that people clone mediawiki/extensions/Parsoid/js/contrib.git instead of using npm install? Probably the best way to solve this issue is to go ahead and migrate to express 3.0. See https://github.com/visionmedia/express/wiki/Migrating-from-2.x-to-3.x and https://github.com/visionmedia/express/wiki/New-features-in-3.x. Anyone want to tackle this? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
