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
I usually use npm pack to test files locally . That has resulted in the tarball install path ending up in a published package before. It would be nice if Publint had a check guarding against packages installed from local files:
I probably need some time to think about this, as right now publint focuses on JS file syntax and exports. Expanding to dependencies checking could be nice as a "publish linter". I think it'll be clearer whether this make sense after implementing #13
I usually use
npm pack
to test files locally . That has resulted in the tarball install path ending up in a published package before. It would be nice if Publint had a check guarding against packages installed from local files:The text was updated successfully, but these errors were encountered: