Skip to content

Conversation

Rich-Harris
Copy link
Member

Queries are cached on the server per-request — that is, calling myQuery() multiple times will only invoke the function once.

At present, the cache key is a combination of the query id and the stringified argument (if there is one), but this doesn't work if the query doesn't have an id, because it isn't exported from a .remote.ts file. This PR fixes it.

Non-exported queries are probably somewhat rare, but this is useful for things like an isAuthenticated() query that's used in multiple places.


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:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

Copy link

changeset-bot bot commented Sep 22, 2025

🦋 Changeset detected

Latest commit: 54444c3

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

@svelte-docs-bot
Copy link


if (cache === undefined) {
cache = {};
(state.remote_data ??= new Map()).set(info, cache);
Copy link
Member

@teemingc teemingc Sep 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use a WeakMap here so that the info object key can be garbage collected?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whole thing will be garbage collected after state becomes obsolete, so I don't think we need it / should do it.

Co-authored-by: Tee Ming <chewteeming01@gmail.com>
@dummdidumm dummdidumm merged commit f360657 into main Sep 22, 2025
22 checks passed
@dummdidumm dummdidumm deleted the non-exported-queries branch September 22, 2025 08:28
@github-actions github-actions bot mentioned this pull request Sep 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants