You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #22, elm-analyze doesn't scan files in node_modules, which is fine by us.
Unfortunately, some of the dependencies in elm.json may be consumed by some of the Elm modules in node_modules. We are therefore seeing false-positive “Unused dependencies” results.
Ideally, the "Unused dependencies" check should factor in Elm code in node_modules, even if the check results exclude it.
An interim work-around for us would also be the option to disable the "Unused dependencies" check, which does not currently seem to be possible in elm-analyse.json.
The text was updated successfully, but these errors were encountered:
In our codebase,
source-directories
points to some libraries innode_modules
:Since #22, elm-analyze doesn't scan files in
node_modules
, which is fine by us.Unfortunately, some of the dependencies in elm.json may be consumed by some of the Elm modules in
node_modules
. We are therefore seeing false-positive “Unused dependencies” results.Ideally, the "Unused dependencies" check should factor in Elm code in
node_modules
, even if the check results exclude it.An interim work-around for us would also be the option to disable the "Unused dependencies" check, which does not currently seem to be possible in
elm-analyse.json
.The text was updated successfully, but these errors were encountered: