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
{{ message }}
This repository has been archived by the owner on Sep 25, 2019. It is now read-only.
I have a project that depends on several lightweight dependencies, so they shouldn't be considered peerDependencies (I don’t want to burden the consumers with installing them manually) but I don't want them not to be bundled, since the library is for both frontend and backend and it should work as expected in Node. Could an option be added that sets a dep to be external even if it's not a peer dependency on the package.json?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a project that depends on several lightweight dependencies, so they shouldn't be considered peerDependencies (I don’t want to burden the consumers with installing them manually) but I don't want them not to be bundled, since the library is for both frontend and backend and it should work as expected in Node. Could an option be added that sets a dep to be external even if it's not a peer dependency on the
package.json
?The text was updated successfully, but these errors were encountered: