Deno 2; Open Source Pledge; TC39 meeting October; language evolution; ES2025; destructuring

• Backwards compatibility with Node.js and npm, allowing you to run existing Node applications seamlessly
• Native support for package.json and node_modules
• Package management with new deno install, deno add, and deno remove commands
• A stabilized standard library
• Support for private npm registries
• Workspaces and monorepo support
• Long Term Support (LTS) releases
• JSR: a modern registry for sharing JavaScript libraries across runtimes

The initiative “Open Source Pledge” wants companies and developers to “pay their share”: “Whether you’re a CEO, CFO, CTO, or just a dev, your company surely depends on Open Source software. It’s time to pay the maintainers.”

Steps for joining:

1. Pay Open Source maintainers: The minimum to participate is $2,000 per year per developer at your company.
2. Self-report annually: Each year, publish a blog post outlining your payments to maintainers.

• Read the blog post for details.
• To get a quick overview, go to this web page with tables.

A presentation at the October TC39 meeting sketches what the future of JavaScript could look like. It’s important to note that these are just preliminary ideas!

Instead of all of JavaScript being implemented by JavaScript engines, we’d have:

• JS0: core language, implemented by JavaScript engines
• JSSugar: syntax features, transpiled to JS0 by tools

JSSugar defines transpilations like those that are already performed by tools such as Babel and TypeScript. One upside is that it eases the workload of JavaScript engine implementers where each new feature increases security risks.