bloglovin / lintlovin Goto Github PK

In the git hook check we should warn or error out if the pushed code doesn't match the checked out code – as the tests will otherwise be run on the wrong code.

If we're doing an app for Node 0.10 or for iojs then we want to ensure that everyone that uses that app uses it with the right node version and even more we want to ensure that the tests that are run are run with the right node version.

As different npm versions can also treat package.json files different we also want to ensure that the npm version is fairly new – if not of the latest version so at least one of the third latest or so.

This should be checked on at least push time.

I didn't not test this properly. But it seems like noMocha has no effect, it still expects a test directory to be around.

Using eg. Max Ogden's https://github.com/maxogden/dependency-check or some alternatives like https://github.com/rumpl/depcheck or https://github.com/dylang/npm-check to parse all used packages and ensure that those and only those are included as dependencies.

This is a good addition to the already existing JSHint checks for unused variables that will remind one to remove the inclusion of non-used modules in the JS-code. An addition like this will ensure that if a module is removed from all JS-files, that the module is also removed as a dependency from the project.

Check out http://jscs.info/ for more information! We'd be glad to help with integration if necessary!

On Windows OS, it is usually not possible to create symlinks, unless you're running in an elevated shell (which is uncommon).

I would recommend a combination of is-windows and is-administrator to detect the situation and warn accordingly.

Running "dependency-check:files" (dependency-check) task Fatal error: No entry paths found

If all files have been ignored in dependencyFiles

Please add a License file.

If it was X time ago that new dependency versions was looked for, then trigger a background process that checks for new dependency versions and updates a local dependency cache.

Then on each test, check that cache for new versions and warn/notify the user about outdated dependencies.

(In the case of an outdated Lintlovin and/or other specified versions, perhaps even throw an error)

Construct this as a new grunt task that can be used independently of Lintlovin.