-
-
Notifications
You must be signed in to change notification settings - Fork 769
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
sinon in npm registry broken with node 0.6.5 #65
Comments
Are you having problems with Sinon or sinon-nodeunit specifically? sinon-nodeunit bundles old versions of both nodeunit and sinon, and I'm thinking of deprecating the package altogether. Sinon in npm does not have this flaw. |
Yeah, I think it's sinon-nodeunit. I thought I saw the same problem with sinon (looked like an update hadn't been published to NPM in a while), but maybe I was mistaken. Just to be clear, the issue isn't node unit it's that node 0.6.5 has removed require.paths from the API. |
I know the issue. Sinon had this issue, but it was solved long ago. I recommend you use vanilla nodeunit and Sinon for now, I don't think I'll update sinon-nodeunit anymore, especially now that buster.js is out in beta (http://busterjs.org) |
Got it, thx! |
node.js finally removed require.paths, the sinon (and sinon-nodeunit) in the NPM registry still have it. Git clone directly into the node_modules folder works fine, please republish.
Here's the output
uncaught undefined: Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.
at Function. (module.js:376:11)
at Object. (/Users/shawn/Developer/node/nodeproj1/node_modules/sinon-nodeunit/deps/sinon/lib/sinon.js:208:12)
The text was updated successfully, but these errors were encountered: