Dev2: "Yeah"
Dev1: "Then why isn't it working?"
Dev2: "Because unlike EVERY OTHER THING called stdlib you need to install this one because it's not actually a stdlib"
Dev1: "..."
Dev2: "Yeah"
Dev1: "Then why isn't it working?"
Dev2: "Because unlike EVERY OTHER THING called stdlib you need to install this one because it's not actually a stdlib"
Dev1: "..."
I expect the easy way to get around this is for folks to refer to us, when speaking technically, as "stdlib.com" ("standard lib dot com").
Also you aren't worried at all about confusion or typosquatting (or what you would call it with a common name) with all the variations of standardlibrary, standardlib, stdlib?
The npm package name standardlibrary was open, let me know if you want it transferred. No charge or bullshit, of course. I just claimed it because it was free and I guessed that somebody would typosquat it sooner or later considering your company name. If not I'll just release it
The way 99.99% of developers have used us to date is starting with our in-browser or CLI tooling which installs / requires the correct package automatically. So I think that removes some of the risk you're talking about. :)
You can hold on to the NPM package for now if you'd like! That's a good one. If we do find typosquatting becomes an issue, do you mind if I reach out?