-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to mocha #31
Switch to mocha #31
Conversation
"test:watch": "watch 'npm test --silent' src test" | ||
"posttest": "npm run lint --silent", | ||
"test": "mocha", | ||
"test:watch": "concurrently -rk 'npm run test --silent -- -w' 'npm run lint:watch'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved lint to posttest
so the lint results show after the tests run. Helps keep linter happy while testing.
@ariporad any ideas why travis / appveyor are not running on this PR? |
I believe it's configured to only run if |
Oh, right, it isn't merged yet :) |
@levithomason I got this error on node v4:
|
Did you try installing deps again, or blowing away and reinstalling? NPM has been having issues with that. |
It looks like |
Hm, checking. |
Thanks! I just used |
Cool, no worries. You are right about the separate packages, but since we have › npm ls babel-register
[email protected] /Users/levithomason/src/shx
`-- [email protected]
`-- [email protected]
› npm ls babel-polyfill
[email protected] /Users/levithomason/src/shx
`-- [email protected]
`-- [email protected] |
After running npm WARN package.json [email protected] No bin file found at lib/cli.js
npm WARN optional dep failed, continuing [email protected]
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
...
$ npm test # this command fails, as before
$ npm ls babel-register
[email protected] /home/nate/PR_31/node_modules/shx
├─┬ [email protected]
│ └── [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]
$ npm ls babel-polyfill
[email protected] /home/nate/PR_31/node_modules/shx
└─┬ [email protected]
└── [email protected] @levithomason Can you successfully re-clone, install deps, and test, all using node v4.2.4? If so, I think this may be an OS difference between Linux and OS X. |
Yeah, retried it again. For me, it all works if those packages are direct dependencies. Please let me know if I'm doing something wrong or if you're seeing something else. |
c81420c
to
8ae49d3
Compare
Confirmed and fixed. npm v3 (node 5) installs modules in a flat tree, which allows requiring deps of other deps. npm v2 (node 4) uses nested node_modules so they cannot be required. Good catch and thanks for testing, I've added the deps explicitly. EDIT In hindsight, it seems crazy to propose we rely on our deps' deps 😬 |
LGTM. Passes for both node v4 and v5. I'll merge this in and rebase the other PR to see if things are working. |
Fixes #22