Deno 1.40; esbuild v0.20.0; ES proposal: explicit resource management; deprecated npm packages

• Temporal API
• import.meta.filename and import.meta.dirname
• ECMAScript decorators

• “We’re introducing a new unstable Deno.UnsafeWindowSurface API to address windowing in Deno. Our goal is to provide a windowing solution for WebGPU without linking to native windowing systems like X11.”

  “This is a low level API that can be used by FFI windowing libraries like sdl2, glfw, raylib, winit and more to create a WebGPU surface using native window and display handles.”

• Backwards-incompatible change in Deno – if you use esbuild in tests, you need to switch:

  /* Old: */ esbuild.stop();
  /* New: */ await esbuild.stop();

• Inside node_modules, esbuild has to pick a filename extension when it is omitted in an import:
  • Default order: .tsx .ts .jsx .js .css .json
  • Previous order in node_modules: .jsx .js .css .json .tsx .ts
  • New order in node_modules: .jsx .js .tsx .ts .css .json
  The reason for this change is explained in the release notes.

“One of my favorite new features of JavaScript [...] is explicit resource management. It brings new syntax, using foobar = ..., that enables RAII [resource acquisition is initialization], reducing boilerplate when managing the lifecycle of various resources.”

async function main() {
  await using connection = await connect();
  await doStuff(connection);
} // connection is closed