search

jgm / djot.js

JavaScript implementation of djot
MIT License
146 stars 16 forks source link

Add the package to the npm registry (www.npmjs.com) when 0.1.0 is released #20

Closed omasanori closed 1 year ago

omasanori commented 1 year ago

I guess anyone won't forget that but just in case...

jgm commented 1 year ago

I think I managed to do this correctly. 0.1.0 failed because the name djot was rejected (too close to dot). So I went for djot-js.

omasanori commented 1 year ago

Thanks!

jgm commented 1 year ago

Actually having second thoughts about the name, and wanted to raise it here because I believe I can still "unpublish" within 24 hours. @matklad would be good to have your feedback too. djot-js is a bit weird because, after all, this is a repository of JavaScript packages, so of course it's js. (But then, it's really ts.) djot-markup seems potentially better, though of course there's a question whether it's really markup. Any thoughts?

matklad commented 1 year ago

Yeah, dj-js is suboptimal for npm. But nothing obviously better comes to mind. djotlang?

jgm commented 1 year ago

djotlang sounds like it should be a programming language. djot-markup is the best alternative I've thought of, don't know if it's good enough to change though. Advantage is that you can see what kind of thing it is from the name.

omasanori commented 1 year ago

@djot/djot? (for flexibility in the future, like splitting the package into @djot/parser and @djot/html-render and making @djot/djot a meta-package for instance) if you can create the djot organization on npmjs.com; it might be rejected like the djot package.

Reference: https://docs.npmjs.com/cli/v9/using-npm/scope

jgm commented 1 year ago

I've got the @djot organization name now. I have unpublished djot-js. So, we could publish as @djot/djot -- is that a normal thing to do? (I think it would let me use the djot name within that namespace, since the worry was just that it was typographically too close to an existing package.)

omasanori commented 1 year ago

Usually scoped packages are named as @foo/core, @foo/cli (for CLI entrypoint), @foo/node (for Node.js support / shim), etc. I think @foo/foo is fine, however.

bpj commented 1 year ago

Is there any published version ATM? I get no matches found for all the above mentioned.

jgm commented 1 year ago

No, I unpublished and have not yet published under new name, because I'm still not quite sure what name to use, but it will probably be @djot/djot.

jgm commented 1 year ago

OK we're live as @djot/djot