$app/paths

import { function asset(file: Asset): string
Resolve 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 <script> 	import { asset } from '$app/paths'; </script>  <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: <a href="{base}/your-page">Link</a>
@deprecatedUse resolve(...) insteadbase, function resolve<T extends RouteId | Pathname>(...args: ResolveArgs<T>): ResolvedPathname
Resolve 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';

<script>
	import { asset } from '$app/paths';
</script>

<img alt="a potato" src={asset('/potato.jpg')} />

import { function resolve<T extends RouteId | Pathname>(...args: ResolveArgs<T>): ResolvedPathname
Resolve 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';

// using a pathname
const const resolved: stringresolved = resolve<"/blog/hello-world">(route: "/blog/hello-world", params: Record<string, string>): ResolvedPathname
Resolve 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`);

// using a route ID plus parameters
const const resolved: stringresolved = resolve<"/blog/[slug]">(route: "/blog/[slug]", params: Record<string, string>): ResolvedPathname
Resolve 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'
});