This is not a coding issue, but maybe an issue to do with marketing and publication. When I briefly looked at the library (which seems super cool!), I was wondering where the NPM link was. So I went to npmjs.com and searched for itr8 and came up short. Not being phased by that, I guessed the name was something else, and checked out the package.json. Turned out I got the name right, after all, which got me all the more confused. Then I scoured the readme and found that one could install it using npm i mftr/itr8
, which I did, and it worked. Confusingly, searching for "mrft/itr8' did not come up with anything as well and https://www.npmjs.com/package/mrft/itr8 was a 404.
Then it dawned on me that you were not using the NPM repo at all and that NPM has a shortcut for GitHub ๐ Which is fine - I have used it myself in the past for distributing patches and whatnot (and then forgot about it), but I am not sure everyone else is as persistent as me ๐ So you might want to consider simply publishing it to NPM, as many will think that it not being there means you need to copy the source and install it locally, which is a dead-sure turn-off. You can still namespace it under @mrft/itr8
if you want to.