denoland-deno/cli/tests/testdata/workers/nonexistent_worker.ts

const w = new Worker(import.meta.resolve("./doesnt_exist.js"), {
  type: "module",
});

w.postMessage("hello");
chore: use import.meta.resolve() in tests (#15256) 2022-07-20 10:56:53 -04:00			`const w = new Worker(import.meta.resolve("./doesnt_exist.js"), {`
fix(runtime): handle race condition in postMessage where worker has terminated (#10239) The panic was caused by the lack of an error class mapping for futures::channel::TrySendError, but it shouldn't have been throwing an error in the first place - when a worker has terminated, postMessage should just return. The issue was that the termination message hadn't yet been recieved, so it was carrying on with trying to send the message. This adds another check on the Rust side for if the channel is closed, and if it is the worker is treated as terminated. 2021-04-19 10:57:02 -04:00			`type: "module",`
			`});`

			`w.postMessage("hello");`