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'm sure there's a reason for publishing the package via GitHub package repo, but it adds complexity for those wishing to use this library -- having to maintain PAT's, manage .npmrc configuration, etc. It also means that anyone wishing to use this library cannot release a public app that depends on it -- they would have to pre-package it.
Would also publishing it to NPM be a bad thing?
The text was updated successfully, but these errors were encountered:
I'm sure there's a reason for publishing the package via GitHub package repo, but it adds complexity for those wishing to use this library -- having to maintain PAT's, manage .npmrc configuration, etc. It also means that anyone wishing to use this library cannot release a public app that depends on it -- they would have to pre-package it.
Would also publishing it to NPM be a bad thing?
The text was updated successfully, but these errors were encountered: