Trying an Introduction to Publishing JSR Packages
JSR is a new package registry for JavaScript. The documentation says it is not a package manager, so be careful not to confuse the two. This time I will create a package in a Hello World-like way.
The way to create a package is extremely simple.
First, prepare a GitHub account. If you do not have one, create one.
Log in from the icon in the upper-right area of the JSR website. Then, from your account icon, you will be able to choose a menu item called "Publish a package."
Next, decide the Scope and Package name. Once you decide these, the JSR package name for publishing is determined. For example, if the package name is greet and it was created by me (karad), the public JSR package name becomes @karad/greet.
After deciding, press the Publish button. The screen then transitions and shows a guidance page for the work that follows.
After that, as written in the Introduction, you only need to prepare the necessary files such as mod.ts and jsr.json, then run $ npx jsr publish. The jsr.json sample appears on the guidance page shown after deciding the package name.
The Hello World-like package I created this time is @karad/greet - JSR.
There are already several greet packages registered that can be created by following the flow above. If you are trying it as a test, I thought it might be better to keep the package name as greet and let it pass through. Of course, if you already have your own package, trying it with that package is also good.
I published a package experimentally by following the sample like this, but can you casually publish a lot of packages and delete them later? The answer was in the FAQ item "Can I delete a package from JSR?"
> Source code published to JSR can not be deleted. > ... > You can "yank" a version of a package, which will hide the version from the default view, but it will still be available to users who depend on it. > ... > You may delete a package if it has no published versions.
Packages with published versions cannot be deleted. They can be hidden by yanking, but users can still use that version if they specify it directly. Also, a package with no published versions can be deleted. So care is required when publishing.
By the way, what is JSR short for? The answer is in the FAQ section of the documentation. It apparently stands for "JavaScript Registry."
> Is "JSR" an initialism for "JavaScript Registry"? > > Yes.
I plan to play with it for a while and get used to it.