-
Notifications
You must be signed in to change notification settings - Fork 365
Remove dependencies from nodeunit git #267
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
Conversation
|
@caolan I'm assuming |
|
@mreinstein that may have been the reasoning at the time, but feel free to remove it if you like - I think most people would expect to have NPM pull in the dependencies now. Also, see the 'deps' directory - there are still some modules in there that probably date to a time before NPM was the clear package manager winner for node |
@caolan if
What should be done with the modules in
|
|
@mreinstein globally installed modules will still have their dependencies installed by default. It's only a breaking change for people that reference the files directly inside their node_modules/nodeunit... which I'd say was an undocumented interface. So I think a minor version bump is OK but it depends how strict you'd like to be. |
|
@caolan it looks like |
|
heh, yeah I'd forgotten about that! the right solution, if you're up for it, is probably to drop the old makefile and use one of the more modern bundlers like browserify or webpack. |
Presumably these cached dependencies shouldn't be committed in nodeunit vcs?