the linter will check for installed version 1.0.0, even though npm resolves duplicate modules in favor of the non-dev dependency version. This error incorrectly suggests that the wrong version is installed (i.e. 0.9.1), when it should instead suggest that MyModule be moved to dependencies.
This scenario is a bit contrived and a result of user error, but caused me a moment of confusion with the utility since the "wrong version" error fails fast and doesn't suggest a duplicate. Took me a minute to spot the duplicate because the "wrong version" was the correct version listed in dependencies. :)
Given the following situation:
the linter will check for installed version 1.0.0, even though
npm
resolves duplicate modules in favor of the non-dev dependency version. This error incorrectly suggests that the wrong version is installed (i.e. 0.9.1), when it should instead suggest that MyModule be moved to dependencies.This scenario is a bit contrived and a result of user error, but caused me a moment of confusion with the utility since the "wrong version" error fails fast and doesn't suggest a duplicate. Took me a minute to spot the duplicate because the "wrong version" was the correct version listed in dependencies. :)