NodeBDD icon indicating copy to clipboard operation
NodeBDD copied to clipboard

installation issue

Open scips opened this issue 11 years ago • 4 comments

Dear, I'm trying your install process but at the third step it fails (npm install). I'm on linux and here is the output. I don't have issue with other node projects.

$ npm install --dev
npm WARN package.json [email protected] No README.md file found!
npm WARN unmet dependency /var/www/github/NodeBDD/node_modules/connect-assets requires underscore@'1.1.7' but will load
npm WARN unmet dependency /var/www/github/NodeBDD/node_modules/underscore,
npm WARN unmet dependency which is version 1.2.2

scips avatar Mar 06 '13 14:03 scips

I'm having the same issue

jessbowers avatar Aug 01 '13 17:08 jessbowers

I am also having this issue :( any resolution?

jdmitch avatar Mar 05 '14 20:03 jdmitch

Seems like the repository includes the node_modules folder (which is where npm install packages)... a quick fix will be to remove that folder and then you can proceed with

npm install --dev

saaguero avatar Jun 11 '14 20:06 saaguero

There are so many deprecated dependancies in this project that it seems unusable in a modern node setup.

$ npm install --dev
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] bugs['web'] should probably be bugs['url'].
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] specifying dependencies as array is deprecated
npm WARN unmet dependency /Users/aaronh/src/NodeBDD/node_modules/connect-assets requires underscore@'1.1.7' but will load
npm WARN unmet dependency /Users/aaronh/src/NodeBDD/node_modules/underscore,
npm WARN unmet dependency which is version 1.2.2

Removing node_modules and running npm install --dev runs into a lot more problems.. here is a small snippet.

npm WARN engine [email protected]: wanted: {"node":">= 0.4.1 < 0.7.0"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN deprecated [email protected]: highlight is deprecated in favor of "highliht.js"
npm WARN engine [email protected]: wanted: {"node":"> 0.4.x < 0.7.0"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN engine [email protected]: wanted: {"node":">= 0.4.1 < 0.5.0"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN deprecated [email protected]: use gulp-rimraf instead
npm WARN engine [email protected]: wanted: {"node":"0.4.x"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN engine [email protected]: wanted: {"node":">= 0.4.1 < 0.7.0"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN excluding symbolic link index.js -> lib/haml.js
npm WARN excluding symbolic link index.js -> lib/connect-form.js
npm WARN excluding symbolic link lib/index.js -> jade.js
npm WARN excluding symbolic link support/sass/index.js -> lib/sass.js
npm WARN engine [email protected]: wanted: {"node":"> 0.4.x < 0.7.0"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN engine [email protected]: wanted: {"node":">= 0.4.1 < 0.5.0"} (current: {"node":"0.10.35","npm":"1.4.28"})
npm WARN excluding symbolic link lib/index.js -> jade.js
npm ERR! fetch failed https://registry.npmjs.org/less/-/less-2.3.1.tgz
npm WARN excluding symbolic link index.js -> lib/sass.js

I stopped after downloading 175MB of deprecated dependancies.

Is there a way to get this fixed? If not, it might be best that this project is no longer linked from https://github.com/cucumber/cucumber-js

aars avatar Feb 06 '15 12:02 aars