You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to support that we need to pass a full location link to package (e.g. https://github.com/user/repo/packages/foobar to the repository field, which isn't recommended in general.
There's also another reason for me to use the repository field that way, and it's because npm's package page doesn't respect repository.directory too (the "repository" link).
The only left possible workaround is to put it on the homepage but if you want to have a website there it's not an option.
For this purpose, we can instead use package-json or such package, to get the current package.json for a package.
The text was updated successfully, but these errors were encountered:
Currently, to support that we need to pass a full location link to package (e.g.
https://github.com/user/repo/packages/foobar
to therepository
field, which isn't recommended in general.There's also another reason for me to use the repository field that way, and it's because npm's package page doesn't respect
repository.directory
too (the "repository" link).The only left possible workaround is to put it on the
homepage
but if you want to have a website there it's not an option.For this purpose, we can instead use
package-json
or such package, to get the current package.json for a package.The text was updated successfully, but these errors were encountered: