It was pointed out in PR #8 that some packages are published under namespaces, and they should be named accordingly, so you should be able to npm i -D @namespace/pkg-name by looking at the list. I'll do a full pass on all of the links. I personally plan to publish under a namespace and would encourage you to consider it. The format should then consistently be:
If a package is not published on npm, I think I'll signal that by removing the style-formatting. It may be appropriate to remove unpublished packages from the list entirely.
For now we're assuming npm and GitHub, but that might need to change eventually.
This increasing complexity also points to the need for a more complete discovery tool that's beyond the scope of this awesome list, as discussed in Svelte's issue 1070, maybe taking inspiration from Ember Observer and Ruby Toolbox. It's been mentioned on Discord a bunch too.
It was pointed out in PR #8 that some packages are published under namespaces, and they should be named accordingly, so you should be able to
npm i -D @namespace/pkg-nameby looking at the list. I'll do a full pass on all of the links. I personally plan to publish under a namespace and would encourage you to consider it. The format should then consistently be:@npm-namespace/published-package-namesub>@github-user</sub - Package descriptionor if there's no npm namespace:
published-package-namesub>@github-user</sub - Package descriptionIf a package is not published on npm, I think I'll signal that by removing the
style-formatting. It may be appropriate to remove unpublished packages from the list entirely.For now we're assuming npm and GitHub, but that might need to change eventually.
This increasing complexity also points to the need for a more complete discovery tool that's beyond the scope of this awesome list, as discussed in Svelte's issue 1070, maybe taking inspiration from Ember Observer and Ruby Toolbox. It's been mentioned on Discord a bunch too.