Basic setup is to put the JSX templates into their own repo; bring that in with your choice of package manager; and each project requires them like any other package code. There are a lot of tutorials out there on setting up a UI/component library so I won't reinvent them here ;)

The main thing you will need to work out is how to make the shared package available, assuming you're not open sourcing it:

• Private NPM modules work well if your team is happy to pay for NPM
• NPM/yarn/etc can pull code from private repositories, using the git URL instead of a version number. Point to the version tag with a hash, eg:

  "dependencies": {
  "yourcomponents": "git+ssh://git@bitbucket.org/account/repo.git#1.2.3"
  }
  

  ...main thing to note about that approach is all your builds will need SSH access as well, so they can access the repo. Also, we found NPM was quite slow pulling from private git repos; and didn't put much feedback onto the screen (worst case was someone on a slow connection getting no Terminal feedback for 10mins). We actually found Bower worked better, but since it's deprecated I wouldn't go there at this point.
• You can self-host modules or use third party (non-NPM) package hosts, but I haven't done it so can't give you much detail.

I suppose you could set them up as dependencies in your project and import them using modules? That way you could have multiple repos and reference them in your package.json.

Thank you for this very informative article. I was able to learn a lot about HTML Templat design by reading this post. Thanks to the author of this post. I used to follow htmltemplates for Html Template Design inspiration. After reading this post I decided to keep your profile on my favorites list.