search

vrugtehagel / yozo

A custom element library for simple, robust and readable components
https://yozo.ooo
5 stars 0 forks source link

Create JSR package #3

Open vrugtehagel opened 6 months ago

vrugtehagel commented 6 months ago

Maybe it'd be nice for Yozo to live on jsr.io. Users should be encouraged to just download a version and use it on their site, but perhaps JSR would increase visibility and allow users to use it with their favorite build tools if they wish.

If doing this, possibly also add type annotations (probably through JSDoc comments, not TypeScript).

vrugtehagel commented 5 months ago

Actually, this might not be such a good idea.

Part of the problem is that it generally doesn't make a lot of sense to have semantic versioning for Yozo, because changes should be in favor of the bundle size and therefore are not backwards compatible by default. This is fine if users are downloading a specific version, because then they are much more aware of upgrades since they need to manually upgrade by downloading the next version. When using semantic versioning through a package manager or registry like JSR or NPM, then a minor version update could break code without users doing anything. Bad experience.

If Yozo wants to fit into the mold of semantic version, I am afraid it is going to just end up with a rather high major version, which is confusing for users since the changes that are made would not be "major" in any shape or form, they would just not be backwards compatible.