Npm-check 5.1 is too zealous while looking for missing modules

Hello! First of all, thanks for your work, I love this helper as I love to keep my projects with depencies up to date!

Anyway since updating to 5.1 I noticed an annoying behaviour: npm-check is starting to look for modules everywhere, even in .eslintrc or karma.conf.js!

The worst part is that I use webpack resolve’s modulesDirectories options to load my modules with absolute paths from the root of my project, so I have a lot of this calls:

import Header from 'components/header' or import * as api from 'utils/api'

Before 5.1 they were ignored, while now they are all caught making the report unreadable:

actions                             �  MISSING!  Not installed.
                                        �  PKG ERR!  Not in the package.json. Found in: \src\scripts\actio
ns\animations.js, \src\scripts\actions\blocks.js, \src\scripts\actions\currentConversation.js, \src\script
s\actions\mail.js, \src\scripts\components\Main.jsx...

and so on.

I tried also with the -s flag but it skips a lot of modules so it’s not viable either.

[alexkuz]

I have similar problems:

• I’m using custom resolve.modules in webpack config, so there are false positives for such modules. Config looks like this:

resolve: {
        modules: [
          'web_modules',
          'node_modules',
          'shared'
        ]
}

I guess it’s not that easy to support this, though (in this example, it would require checking every nested shared folder in project).

• Unsupported webpack loaders syntax (like !!style!css?modules!postcss!.). This issue is more common, I believe, and is probably easier to fix: split by !, normalize loader names (style -> style-loader) and then check them, something like that.

[ramusus]

The same here, when using webpack aliases:

    resolve: {
        modules: ['node_modules', 'bower_components'],
        descriptionFiles: ['package.json'],
        extensions: ['.js', '.jsx'],
        alias: {
            libs: path.join(__dirname, 'assets/libs'),
            tests: path.join(__dirname, 'assets/tests'),
            stores: path.join(__dirname, 'assets/stores'),
            components: path.join(__dirname, 'assets/components'),
        },
    },