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
While reviewing the latest changes to this package, I noticed that the latest packaged version of this module on NPM appears to (now) include a bunch of files under memo-parser/node_modules, as shown here: https://diff.intrinsic.com/eslint-plugin-import/2.19.1/2.20.0
I expect fixing this would simply require adding this path to .gitignore (in the absence of a .npmignore). I see "node_modules" is already there, perhaps NPM is processing this as the top level directory only.
The text was updated successfully, but these errors were encountered:
ah nvm, turns out this package is unfortunately using the dangerous files field, without excluding nested node_modules. I'll fix this for the next release.
While reviewing the latest changes to this package, I noticed that the latest packaged version of this module on NPM appears to (now) include a bunch of files under
memo-parser/node_modules
, as shown here: https://diff.intrinsic.com/eslint-plugin-import/2.19.1/2.20.0I expect fixing this would simply require adding this path to .gitignore (in the absence of a .npmignore). I see "node_modules" is already there, perhaps NPM is processing this as the top level directory only.
The text was updated successfully, but these errors were encountered: