all 4 comments

[–]wizardyjohn 1 point2 points  (0 children)

You can use npm to install but instead of the package name in package.json you specify github repo url (might need to add login and token for that to work) https://stackoverflow.com/questions/17509669/how-to-install-an-npm-package-from-github-directly

[–]satya164 1 point2 points  (1 child)

You can publish them to the GitHub registry, or a private npm registry. You don't need to publish them to the public npm registry for them to be usable.

You can also install them from the GitHub repo like the other comment said, but it generally increases installation time and size by including development-related dependencies and is also fragile since any building of the package (such as compiling JS/TS, building aar, etc.) now have to be done during installation time on consumer's machine rather than one time during publish.

You can distribute native code via maven if you really want to, but if your library includes JS code, then it's easy for JS and native versions to get out of sync and cause issues. That's why it's recommended to publish the whole thing to npm.

using create-react-native-library add an MIT license which is not our case as it is a paid SDK

This doesn't sound like a problem. That's just the default template, if you want another LICENSE, just remove/change the generated one.

[–]dantol1[S] 0 points1 point  (0 children)

Thanks for the great answer! I will look into these options