The big news is that Deno is moving away from type checking before running code: The new subcommand deno check type-checks a project. It’s a first step towards a future where deno run doesn’t type-check anymore (unless you ask it to via --check).

Other highlights:

• Uncaught exceptions are handled like in browsers via "error" events and reportError(error).
• Several improvements in Deno’s Visual Studio Code extension
• deno fmt and deno lint use caches to operate incrementally.
• The Deno.run() API for spawning subprocesses will eventually be replaced by three APIs:
  • The high-level Deno.spawn()
  • The high-level Deno.spawnSync()
  • The low-level Deno.spawnChild()
• Improvements for deno test: better formatting of user output, better errors and stack traces, BDD-style testing, mocking utilities, snapshot testing, FakeTime for time-related tests

Inline variables, invert conditions, extract text from strings. And much more. With the P42 JavaScript Assistant.

Many people leave lots of money on the table when accepting a new job because of the lack of transparency in tech salaries.
talent.io analyzed over 100,000 job offers to give software engineers a clear picture of:

• Salaries and daily rates
• Most in-demand technologies and jobs
• Remote work

Highlights:

• Fetch API
• Web Streams API
• Built-in test runner

Beth Griggs (Node.js release lead) and Michael Dawson (Node.js TSC Chair) talk about:

• Node.js 18, the latest release
• Its most exciting features
• How you can help improve it before it enters long-term support (LTS) on 2022-10-25

Changes:

• Web Extension manifest v3 support
• Support for __dirname and __filename in Node.js targets
• in expressions with process.env ('someProp' in process.env)
• Bug fixes

Before V8 v9.7, the initialization of public fields, private fields and private methods in classes was much slower than assigning to properties. This issue is now fixed. The blog post describes how that was achieved.

TAP is a standard text-based output format for test runners that enables custom formatters and other tooling. TAP 14 is the latest version – seven years in the making! Quoting TAP’s creator, Isaac Z. Schlueter: “The goal this time around will be to make small uncontroversial changes, which can step us into paving the paths laid by node-tap, Test::More, tappy, and many others over the years. There will be no innovation here, just cataloging what exists.”

New features:

• YAML diagnostic blocks must be valid YAML and indented 2 spaces.
• Subtests provide a way to nest one TAP 14 stream inside another.
• A Pragma provides information to a Harness to control its behavior or configure it in some way. Each Pragma line represents a single boolean switch which can be set to true or false.