I thought the only option to work around this was to commit our dist folder to Git. That way npm gets your compiled assets and doesn’t need to know anything about your build process.īut when you install your package directly from Git, those compiled assets aren’t there, because we’ve added them to the gitignore file. When you host your package on npm, you explicitly run a publish command, which runs locally and has access to your compiled assets. Use the “prepare” script to build your library
Instead, you should consider making it available as an npm package.
#Npm install from github branch download#
You could simply provide download links for the CSS and other assets, but then your users can’t easily get any updates to the pattern library. So you’ve got a pattern library: Congratulations! The next step is making it possible for other people to use those patterns.