docs: remote files can be in lib or routes dir

[jycouet]

First step for #14077

---

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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 818441c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-14091-svelte.vercel.app/

[aster-void]

Could you make this sound more like a warning (you can't place remote files outside of...) rather than giving permission (you can place them inside...)? People would naturally assume it's allowed everywhere, since .server.js/ts files can be placed anywhere.

[jycouet]

Could you make this sound more like a warning (you can't place remote files outside of...) rather than giving permission (you can place them inside...)? People would naturally assume it's allowed everywhere, since .server.js/ts files can be placed anywhere.

It was to sound positive of what is handled. But you are maybe right... I don't know.

Currently putting remote flies inside lib files and importing server variables like db, auth causes
Cannot import $lib/server/myfunction.remote.ts into client-side code. This could leak sensitive information.

This is maybe another issue ?!
Having the /server/ segment in the path ?
Because it should be possible to use server stuff in remote files.

[aster-void]

Currently putting remote flies inside lib files and importing server variables like db, auth causes
Cannot import $lib/server/myfunction.remote.ts into client-side code. This could leak sensitive information.

This may be because files under src/lib/server are considered server modules, just like .server.js/ts, and cannot be imported by client module. That seems like a big foot gun as well, but should be handled by another PR (imo).

[eltigerchino]

Thanks for this! Wasn't sure if my suggestion was too strongly worded with the "must" inserted into it but I'm sure that can be changed in the future if someone can phrase it better (or we remove it entirely with your other PR).