resolve relative cookie paths before storing

[Rich-Harris]

per #9299 (comment), this resolve relative (same-domain) cookie paths before storing them locally. It doesn't affect the behaviour of cookies in the browser, but means that if you do this...

cookies.set('a', 'b', { path: '.' });
console.log(cookies.get('a'));

...it will correctly log b instead of trying to retrieve the cookie from headers. Super niche bug that AFAIK no-one has hit, but now that we're explicitly recommending that people use relative paths, it makes sense to fix it.

Tested locally, didn't add one to this PR because it's covered in version-2.

Please don't delete this checklist! 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 pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1629d85

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

This PR includes changesets to release 1 package

Name	Type
@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