SvelteKitReference

$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.
@examplesvelte &#x3C;script> 	import { asset } from '$app/paths'; &#x3C;/script>  &#x3C;img alt="a potato" src={asset('potato.jpg')} /> 
@since2.26asset, 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.
@deprecatedUse asset(...) insteadassets, let base: "" | `/${string}`A string that matches config.kit.paths.base.
Example usage: &#x3C;a href="{base}/your-page">Link&#x3C;/a>
@deprecatedUse resolve(...) insteadbase, 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.
@examplejs import { resolve } from '$app/paths';  // using a pathname const resolved = resolve(`/blog/hello-world`);  // using a route ID plus parameters const resolved = resolve('/blog/[slug]', { 	slug: 'hello-world' }); 
@since2.26resolve, function resolveRoute<T extends RouteId | Pathname>(...args: ResolveArgs<T>): ResolvedPathname@deprecatedUse resolve(...) insteadresolveRoute } 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.assets est fournie, elle sera remplacé par '/_svelte_kit_assets' lors de vite dev ou vite 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}`;

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.
@examplejs import { resolve } from '$app/paths';  // using a pathname const resolved = resolve(`/blog/hello-world`);  // using a route ID plus parameters const resolved = resolve('/blog/[slug]', { 	slug: 'hello-world' }); 
@since2.26resolve } from '$app/paths';

// avec un chemin
const const resolved: ResolvedPathnameresolved = resolve<string>(...args: [route: string] | [route: string, params: RouteParams<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.
@examplejs import { resolve } from '$app/paths';  // using a pathname const resolved = resolve(`/blog/hello-world`);  // using a route ID plus parameters const resolved = resolve('/blog/[slug]', { 	slug: 'hello-world' }); 
@since2.26resolve(`/blog/hello-world`);

// avec un ID de route et ses paramètres
const const resolved: ResolvedPathnameresolved = resolve<string>(...args: [route: string] | [route: string, params: RouteParams<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.
@examplejs import { resolve } from '$app/paths';  // using a pathname const resolved = resolve(`/blog/hello-world`);  // using a route ID plus parameters const resolved = resolve('/blog/[slug]', { 	slug: 'hello-world' }); 
@since2.26resolve('/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

précédent suivant

$app/navigation $app/server