3 ms·
really? its as easy as putting it on github and publishing it in npm.
by sabarasaba 7y ago
really? its as easy as putting it on github and publishing it in npm.
- mlejva 7y agoIt just feels as such a hassle and overkill to maintain another repo/package just for a few components. Another problem is that usually, I realize I want to change the basic component while I'm using it in a different project. So now I have to open another workspace, update it, and publish. Then `npm update` in the project where I'm using my component... I just feel it should be much easier.
- quickthrower2 7y agoGit submodules might be worth considering. It’s like having the dependency copy pasted into your project so you can modify it. Different projects can pin to different versions of the submodule.