mirror of
https://github.com/denoland/deno.git
synced 2024-12-24 16:19:12 -05:00
1.9 KiB
1.9 KiB
Program lifecycle
Deno supports browser compatible lifecycle events: load
and unload
. You can
use these events to provide setup and cleanup code in your program.
Listener for load
events can be asynchronous and will be awaited. Listener for
unload
events need to be synchronous. Both events cannot be cancelled.
Example:
// main.ts
import "./imported.ts";
const handler = (e: Event): void => {
console.log(`got ${e.type} event in event handler (main)`);
};
window.addEventListener("load", handler);
window.addEventListener("unload", handler);
window.onload = (e: Event): void => {
console.log(`got ${e.type} event in onload function (main)`);
};
window.onunload = (e: Event): void => {
console.log(`got ${e.type} event in onunload function (main)`);
};
// imported.ts
const handler = (e: Event): void => {
console.log(`got ${e.type} event in event handler (imported)`);
};
window.addEventListener("load", handler);
window.addEventListener("unload", handler);
window.onload = (e: Event): void => {
console.log(`got ${e.type} event in onload function (imported)`);
};
window.onunload = (e: Event): void => {
console.log(`got ${e.type} event in onunload function (imported)`);
};
console.log("log from imported script");
Note that you can use both window.addEventListener
and
window.onload
/window.onunload
to define handlers for events. There is a
major difference between them, let's run example:
$ deno run main.ts
log from imported script
log from main script
got load event in onload function (main)
got load event in event handler (imported)
got load event in event handler (main)
got unload event in onunload function (main)
got unload event in event handler (imported)
got unload event in event handler (main)
All listeners added using window.addEventListener
were run, but
window.onload
and window.onunload
defined in main.ts
overridden handlers
defined in imported.ts
.