-
Notifications
You must be signed in to change notification settings - Fork 99
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestintegrationsmaintenanceIssue about maintenance (CI, tests, refacto...)Issue about maintenance (CI, tests, refacto...)
Description
Why JSR
- https://jsr.io/docs/why
- primarily because it is the default registry for
deno
, but also it's striving to be (and already is a superset of) the replacement fornpm
with the goal of supporting every runtime equally - secondarily, because it auto-generates documentation, easily switchable between versions, this way we wouldn't need
typedoc
and additional build step for it and configuration https://jsr.io/docs/writing-docs- we should also replace the lengthy README.md documentation with a link to the superior JSR page, but really we should already be doing this with the typedoc docs on github pages
- it also builds everything from TypeScript source files, so we wouldn't need any build step, at least not for JSR, in theory, still need to experiment with this
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestintegrationsmaintenanceIssue about maintenance (CI, tests, refacto...)Issue about maintenance (CI, tests, refacto...)