rjz / es6-client-boilerplate

Starting point for client-side es6 projects
Other
5 stars 1 forks source link

it throws on setup #2

Open ghost opened 9 years ago

ghost commented 9 years ago

Hi. Your script show me some errors on the npm install, and when I try to run a test case, this shows up:

C:\xampp\htdocs\babel> npm test

es6-client-boilerplate@0.0.1 pretest C:\xampp\htdocs\babel eslint ./src

es6-client-boilerplate@0.0.1 test C:\xampp\htdocs\babel ./node_modules/karma/bin/karma start ./karma.config.js --single-run

'.' is not recognized as an internal or external command, operable program or batch file. npm ERR! Test failed. See above for more details.

ghost commented 9 years ago

If you try to run Karma directly

karma start karma.config --single-run

it will find the file, but throw this:

AppData\Roaming\npm\node_modules\karma\node_modules\di\lib\injector.js:9 throw error('No provider for "' + name + '"!'); ^ Error: No provider for "framework:jasmine"! (Resolving: framework:jasmine)

rjz commented 9 years ago

Thanks for reporting! I honestly haven't tested on windows, so I'm looking forward to knocking these out.

'.' is not recognized as an internal or external command, operable program or batch file.

Does this error go away if the current-directory prefixes in the test command in package.json are removed?

"pretest": "node_modules/.bin/eslint src",
"test": "node_modules/karma/bin/karma start karma.config.js",

Error: No provider for "framework:jasmine"! (Resolving: framework:jasmine)

Likewise, does this error go away when the karma-* frameworks are installed globally?

> npm install -g karma-jasmine karma-sinon
ghost commented 9 years ago

I re-installed and tried the changes out.

If I do npm test I would get:

eslint src

es6-client-boilerplate@0.0.1 test C:\xampp\htdocs\babel node_modules/karma/bin/karma start karma.config.js

'node_modules' is not recognized as an internal or external command, operable program or batch file. npm ERR! Test failed. See above for more details. C:\xampp\htdocs\babel>

rjz commented 9 years ago

@Kflash, thanks again for jumping on this and helping debug! I've pushed one more adjustment (tested on win7 / node 0.12) that should clear this up.