Either we revert back to the old behavior and only exclude the top node_modules by default (which is what eslint is doing) or we also exclude nested ones by default.
@kirbysayshi Ok I think we are going to revert to previous behavior in 2.x and users will have to specify nested node_modules themselves since that isn't as common of a use case.
Coverage remained the same at 96.777% when pulling 675f9f2e727a61893f1dfadd5b671b5109817933 on revert-nested-node-modules into 9ce1c9bd58d9a860b4d49ea8bba7b794ba7a75ab on master.
This reverts commit 908bd20654723eac98949f994710c9ea902fe671.
Fixes https://github.com/jscs-dev/node-jscs/issues/2221
Either we revert back to the old behavior and only exclude the top node_modules by default (which is what eslint is doing) or we also exclude nested ones by default.