API de composant impérative

const componentconst component: any = new Componentany(optionsany);

import App(alias) type App = SvelteComponent<Record<string, any>, any, any>
(alias) const App: LegacyComponentType
import App from './App.svelte';

const appconst app: SvelteComponent<Record<string, any>, any, any> = new App(alias) new App(o: ComponentConstructorOptions): SvelteComponent
import App({
	target(property) ComponentConstructorOptions<Record<string, any>>.target: Document | Element | ShadowRoot: documentvar document: Document
window.document returns a reference to the document contained in the window.
MDN Reference
.body(property) Document.body: HTMLElement
The Document.body property represents the  or  node of the current document, or null if no such element exists.
MDN Reference
,
	props(property) ComponentConstructorOptions<Record<string, any>>.props?: Record<string, any> | undefined: {
		// en supposant que App.svelte contient quelque chose
		// comme `export let answer`
		answer(property) answer: number: 42
	}
});

import App(alias) type App = SvelteComponent<Record<string, any>, any, any>
(alias) const App: LegacyComponentType
import App from './App.svelte';

const appconst app: SvelteComponent<Record<string, any>, any, any> = new App(alias) new App(o: ComponentConstructorOptions): SvelteComponent
import App({
	target(property) ComponentConstructorOptions<Record<string, any>>.target: Document | Element | ShadowRoot: documentvar document: Document
window.document returns a reference to the document contained in the window.
MDN Reference
.querySelector(method) ParentNode.querySelector<Element>(selectors: string): Element | null (+4 overloads)
Returns the first element that is a descendant of node that matches selectors.
MDN Reference
('#server-rendered-html'),
	hydrate(property) ComponentConstructorOptions<Record<string, any>>.hydrate?: boolean | undefined: true
});

componentany.$setany(propsany);

componentany.$setany({ answer(property) answer: number: 42 });

componentany.$onany(evany, callbackany);

const offconst off: any = componentany.$onany('selected', (event(parameter) event: any) => {
	consolenamespace console
var console: Console
The console module provides a simple debugging console that is similar to the
JavaScript console mechanism provided by web browsers.
The module exports two specific components:

A Console class with methods such as console.log(), console.error() and console.warn() that can be used to write to any Node.js stream.
A global console instance configured to write to process.stdout and
process.stderr. The global console can be used without importing the node:console module.

Warning: The global console object's methods are neither consistently
synchronous like the browser APIs they resemble, nor are they consistently
asynchronous like all other Node.js streams. See the note on process I/O for
more information.
Example using the global console:
console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(new Error('Whoops, something bad happened'));
// Prints error message and stack trace to stderr:
//   Error: Whoops, something bad happened
//     at [eval]:5:15
//     at Script.runInThisContext (node:vm:132:18)
//     at Object.runInThisContext (node:vm:309:38)
//     at node:internal/process/execution:77:19
//     at [eval]-wrapper:6:22
//     at evalScript (node:internal/process/execution:76:60)
//     at node:internal/main/eval_string:23:3

const name = 'Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
const out = getStreamSomehow();
const err = getStreamSomehow();
const myConsole = new console.Console(out, err);

myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');
// Prints: hello world, to out
myConsole.error(new Error('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err

const name = 'Will Robinson';
myConsole.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to err
source
.log(method) Console.log(message?: any, ...optionalParams: any[]): void (+1 overload)
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3)
(the arguments are all passed to util.format()).
const count = 5;
console.log('count: %d', count);
// Prints: count: 5, to stdout
console.log('count:', count);
// Prints: count: 5, to stdout
See util.format() for more information.
v0.1.100
(event(parameter) event: any.detailany.selectionany);
});

offconst off: any();

componentany.$destroyany();

componentany.propany;

componentmodule component.prop(property) component.prop: any = valueany;

consolenamespace console
var console: Console
The console module provides a simple debugging console that is similar to the
JavaScript console mechanism provided by web browsers.
The module exports two specific components:

A Console class with methods such as console.log(), console.error() and console.warn() that can be used to write to any Node.js stream.
A global console instance configured to write to process.stdout and
process.stderr. The global console can be used without importing the node:console module.

Warning: The global console object's methods are neither consistently
synchronous like the browser APIs they resemble, nor are they consistently
asynchronous like all other Node.js streams. See the note on process I/O for
more information.
Example using the global console:
console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(new Error('Whoops, something bad happened'));
// Prints error message and stack trace to stderr:
//   Error: Whoops, something bad happened
//     at [eval]:5:15
//     at Script.runInThisContext (node:vm:132:18)
//     at Object.runInThisContext (node:vm:309:38)
//     at node:internal/process/execution:77:19
//     at [eval]-wrapper:6:22
//     at evalScript (node:internal/process/execution:76:60)
//     at node:internal/main/eval_string:23:3

const name = 'Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
const out = getStreamSomehow();
const err = getStreamSomehow();
const myConsole = new console.Console(out, err);

myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');
// Prints: hello world, to out
myConsole.error(new Error('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err

const name = 'Will Robinson';
myConsole.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to err
source
.log(method) Console.log(message?: any, ...optionalParams: any[]): void (+1 overload)
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3)
(the arguments are all passed to util.format()).
const count = 5;
console.log('count: %d', count);
// Prints: count: 5, to stdout
console.log('count:', count);
// Prints: count: 5, to stdout
See util.format() for more information.
v0.1.100
(componentany.countany);
componentany.countany += 1;

const resultconst result: any = Componentany.renderany(...)

requirevar require: NodeJS.Require
(id: string) => any
Used to import modules, JSON, and local files.
v0.1.13
('svelte/register');

const Appnamespace App
const App: any
It's possible to tell SvelteKit how to type objects inside your app by declaring the App namespace. By default, a new project will have a file called src/app.d.ts containing the following:
declare global {
	namespace App {
		// interface Error {}
		// interface Locals {}
		// interface PageData {}
		// interface PageState {}
		// interface Platform {}
	}
}

export {};
The export {} line exists because without it, the file would be treated as an ambient module which prevents you from adding import declarations.
If you need to add ambient declare module declarations, do so in a separate file like src/ambient.d.ts.
By populating these interfaces, you will gain type safety when using event.locals, event.platform, and data from load functions.
 = requirevar require: NodeJS.Require
(id: string) => any
Used to import modules, JSON, and local files.
v0.1.13
('./App.svelte').defaultany;

const { headconst head: any, htmlconst html: any, cssconst css: any } = Appnamespace App
const App: any
It's possible to tell SvelteKit how to type objects inside your app by declaring the App namespace. By default, a new project will have a file called src/app.d.ts containing the following:
declare global {
	namespace App {
		// interface Error {}
		// interface Locals {}
		// interface PageData {}
		// interface PageState {}
		// interface Platform {}
	}
}

export {};
The export {} line exists because without it, the file would be treated as an ambient module which prevents you from adding import declarations.
If you need to add ambient declare module declarations, do so in a separate file like src/ambient.d.ts.
By populating these interfaces, you will gain type safety when using event.locals, event.platform, and data from load functions.
.renderany({
	answer(property) answer: number: 42
});

const { headconst head: any, htmlconst html: any, cssconst css: any } = Appany.renderany(
	// props
	{ answer(property) answer: number: 42 },
	// options
	{
		context(property) context: Map<string, string>: new Mapvar Map: MapConstructor
new <string, string>(iterable?: Iterable<readonly [string, string]> | null | undefined) => Map<string, string> (+3 overloads)([['context-key', 'context-value']])
	}
);