Add homepage to package.json

[frederikhors]

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: a4b703f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
@sveltejs/adapter-begin	Patch
@sveltejs/adapter-cloudflare-workers	Patch
@sveltejs/adapter-netlify	Patch
@sveltejs/adapter-node	Patch
@sveltejs/adapter-static	Patch
@sveltejs/adapter-vercel	Patch
create-svelte	Patch
@sveltejs/kit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Conduitry]

Any changes to this file should be indented with tabs like the rest of the file, not with spaces.

I'm not sure how valuable of a change this is, but I would argue that, if we did add a homepage, it should be https://kit.svelte.dev/ - There is a separate package.json field for the repository URL.

[frederikhors]

Any changes to this file should be indented with tabs like the rest of the file, not with spaces.

I'm not sure how valuable of a change this is, but I would argue that, if we did add a homepage, it should be https://kit.svelte.dev/ - There is a separate package.json field for the repository URL.

Done.

[antony]

Where does this information appear? We have this info in the root package, and if we wanted to put it in sub-packages, we'd want to put it into all of them rather than just one.

[dummdidumm]

This will appear on npm, there will be links to the homepage/github repo then, which I agree should be done for all packages. To me it's always a little strange to see a package on npm without any link to github, which makes me think it's closed source or something like that.

[benmccann]

this change seems like a good idea to me, but agree that it should be done for everything under packages/

[frederikhors]

this change seems like a good idea to me, but agree that it should be done for everything under packages/

Done!

[benmccann]

I was starting to suggest that the homepage for the adapters should be their directory in GitHub since that's where the docs for them are, but I think I changed my mind on that because the README already gets published on npm, so there's no value in clicking through to GitHub to see it

Lgtm!

[benmccann]

Is this supposed to be visible on npm? I don't see it https://www.npmjs.com/package/@sveltejs/adapter-static/v/1.0.0-next.19

[bluwy]

It should be, but maybe it's because npm only parses the links based on the latest tag, not the next tag.