$app/paths
import { function asset(file: Asset): stringResolve the URL of an asset in your static directory, by prefixing it with config.kit.paths.assets if configured, or otherwise by prefixing it with the base path.
During server rendering, the base path is relative and depends on the page currently being rendered.
asset, let assets: "" | `https://${string}` | `http://${string}` | "/_svelte_kit_assets"An absolute path that matches config.kit.paths.assets.
If a value for config.kit.paths.assets is specified, it will be replaced with '/_svelte_kit_assets' during vite dev or vite preview, since the assets don’t yet live at their eventual URL.
assets, let base: "" | `/${string}`A string that matches config.kit.paths.base.
Example usage: <a href="{base}/your-page">Link</a>
base, function match(url: Pathname | URL | (string & {})): Promise<{
id: RouteId;
params: Record<string, string>;
} | null>
Match a path or URL to a route ID and extracts any parameters.
match, function resolve<T extends RouteId | Pathname>(...args: ResolveArgs<T>): ResolvedPathnameResolve a pathname by prefixing it with the base path, if any, or resolve a route ID by populating dynamic segments with parameters.
During server rendering, the base path is relative and depends on the page currently being rendered.
resolve, function resolveRoute<T extends RouteId | Pathname>(...args: ResolveArgs<T>): ResolvedPathnameresolveRoute } from '$app/paths';asset
Disponible depuis la version 2.26
Résout l’URL d’un asset se trouvant dans votre dossier static, en le préfixant avec
config.kit.paths.assets si configuré, ou avec le chemin de base
sinon.
Lors du rendu côté serveur, le chemin de base est relatif et dépend de la page en train d’être rendue.
<script>
import { asset } from '$app/paths';
</script>
<img alt="a potato" src={asset('/potato.jpg')} />function asset(file: Asset): string;assets
Utilisez plutôt
asset(...)
Un chemin absolu qui matche config.kit.paths.assets.
Si une valeur de
config.kit.paths.assetsest fournie, elle sera remplacé par'/_svelte_kit_assets'lors devite devouvite preview, puisque les assets ne sont pas encore placés sur leur URL future.
let assets:
| ''
| `https://${string}`
| `http://${string}`
| '/_svelte_kit_assets';base
Utilisez plutôt
resolve(...)
Une chaîne de caractères qui matche config.kit.paths.base.
Exemple d’usage : <a href="{base}/your-page">Link</a>
let base: '' | `/${string}`;match
Disponible depuis la version 2.52.0
Fait correspondre un chemin ou une URL à un ID de route et en extrait les paramètres.
import { function match(url: Pathname | URL | (string & {})): Promise<{
id: RouteId;
params: Record<string, string>;
} | null>
Match a path or URL to a route ID and extracts any parameters.
match } from '$app/paths';
const const route: {
id: RouteId;
params: Record<string, string>;
} | null
route = await function match(url: Pathname | URL | (string & {})): Promise<{
id: RouteId;
params: Record<string, string>;
} | null>
Match a path or URL to a route ID and extracts any parameters.
match('/blog/hello-world');
if (const route: {
id: RouteId;
params: Record<string, string>;
} | null
route?.id: string | undefinedid === '/blog/[slug]') {
const const slug: stringslug = const route: {
id: RouteId;
params: Record<string, string>;
}
route.params: Record<string, string>params.stringslug;
const const response: Responseresponse = await function fetch(input: string | URL | Request, init?: RequestInit): Promise<Response> (+1 overload)fetch(`/api/posts/${const slug: stringslug}`);
const const post: anypost = await const response: Responseresponse.Body.json(): Promise<any>json();
}function match(
url: Pathname | URL | (string & {})
): Promise<{
id: RouteId;
params: Record<string, string>;
} | null>;resolve
Disponible depuis la version 2.26
Résout un chemin en le préfixant avec le chemin de base, s’il existe, ou avec un ID de route en remplissant les segments dynamiques avec des paramètres.
Lors du rendu côté serveur, le chemin de base est relatif et dépend de la page en train d’être rendue.
import { function resolve<T extends RouteId | Pathname>(...args: ResolveArgs<T>): ResolvedPathnameResolve a pathname by prefixing it with the base path, if any, or resolve a route ID by populating dynamic segments with parameters.
During server rendering, the base path is relative and depends on the page currently being rendered.
resolve } from '$app/paths';
// avec un chemin
const const resolved: stringresolved = resolve<"/blog/hello-world">(route: "/blog/hello-world", params: Record<string, string>): ResolvedPathnameResolve a pathname by prefixing it with the base path, if any, or resolve a route ID by populating dynamic segments with parameters.
During server rendering, the base path is relative and depends on the page currently being rendered.
resolve(`/blog/hello-world`);
// avec un ID de route et ses paramètres
const const resolved: stringresolved = resolve<"/blog/[slug]">(route: "/blog/[slug]", params: Record<string, string>): ResolvedPathnameResolve a pathname by prefixing it with the base path, if any, or resolve a route ID by populating dynamic segments with parameters.
During server rendering, the base path is relative and depends on the page currently being rendered.
resolve('/blog/[slug]', {
slug: stringslug: 'hello-world'
});function resolve<T extends RouteId | Pathname>(
...args: ResolveArgs<T>
): ResolvedPathname;resolveRoute
Utilisez plutôt
resolve(...)
function resolveRoute<T extends RouteId | Pathname>(
...args: ResolveArgs<T>
): ResolvedPathname;Modifier cette page sur Github llms.txt