Naming confusion about itr8

[mrft]

Good point.

I am still polishing things to get to a state that I think is 'ready for publication', which is also why I feel in today's world it should be an ESM rather than a CJS module (but I was having a few issues along the way as you are aware).

Personally I don't see a lot of benefit in publishing to npm, since installing straight from github works just as well, but you are right that that is what everyone expects so it will only confuse people if it is not to be found on npmjs.
.
As you can see, marketing is not my strong suit :)

Thanks for being so persistent :)

[fatso83]

Coolio.

P.S. I just went through the excruciatingly painful process of getting a package to work with typescript, new and old Node versions, so you might be able to catch some inspiration on that polish part from the package.json setup (https://github.com/fatso83/retry-dynamic-import). Lots of info in the Git logs for why/what.

[mrft]

@fatso83: https://www.npmjs.com/package/itr8

Closing this issue.

[mrft]

I am somehow glad to hear that you also found it painful...
But great to know a place to check how other people solved it. Might give me some inspiration if I'm stuck.

I think I have it working now though (both module types + both a 'normal' version and a bundled&minified version). I've done an internal thing before using esbuild, but here I wanted to do it solely with tsc. Everything is still in a branch currently, but I'm hoping to release it soon.

I am also working on the npm publishing part. I guess I'll put it out there as-is, not following semver until I think it's stable and mature enough to move to a 1.0 version.