jsr-feedback

34 threads · Page 1 of 1

Package Scope search 5 messages
Example code in the readme is not recognized 4 messages
Release date bug 3 messages
TLS 1.0 & 1.1 5 messages
Why jsr specifier needed ? 9 messages
Rearrange Deprecated Packages to the Bottom of the List 7 messages
Workspaces and local JSR resolution 9 messages
Badge images are cached for too long 8 messages
replace runtime version management as a jsr cli 2 messages
feature
JSR Changelog 2 messages
registry docs enhancement
Better Module Search 8 messages
registry feature
Unable to import a pre-release version with build metadata 2 messages
using packages
Documentations around CLI packages? 5 messages
using packages docs enhancement feature
npm: specifiers need package.json? 4 messages
how to develop locally? 3 messages
Bundling 2 messages
How do I remap JSR imports to local modules from within examples or tests? 9 messages
using packages publishing
`jsr.json` using JSON is a mistake 5 messages
percentage score looks negative 3 messages
Scope names starting with a digit 3 messages
HTTPS modules not supported in JSR packages 3 messages
using packages publishing
WASM module support 2 messages
My thoughts on creeping import magic 2 messages
using packages registry
Export all modules or via a glob 4 messages
publishing
Why not adopt package.json? 20 messages
registry publishing
/meta.json not having exports for specific packages 108 messages
How about reserving a famous scope name? 2 messages
registry
packages that do not support node should not show npm installation instructions 2 messages
Show GitHub Stars, License and Download count 11 messages
Fix: make HEAD method requests return same headers as GET method requests 54 messages
enhancement
Malformed request: Missing query parameter 'config' (while publishing) 5 messages
Typos in docs 4 messages
Images are not displayed inline by default in markdown docs 2 messages
registry docs
Add a main package for a scope 21 messages
registry enhancement feature