For me, the biggest excitement is around "Easier Implicit Returns for undefined-Returning Functions". It's nice not to have to insert a return undefined; when that's the implicit behavior.

cross-posted from: https://lemmy.ml/post/642690

An introductory article on how to leverage some basic mathematical tricks and widely available browser APIs to generate beautiful animations.

Here’s a quick list of what’s new in TypeScript 4.9!

• The satisfies Operator
• Unlisted Property Narrowing with the in Operator
• Auto-Accessors in Classes
• Checks For Equality on NaN
• File-Watching Now Uses File System Events
• "Remove Unused Imports" and "Sort Imports" Commands for Editors
• Go-to-Definition on return Keywords
• Performance Improvements
• Correctness Fixes and Breaking Changes

My (probably controversial) take on why the barrel exports pattern can be harmful.

One of the great advantages of Deno is the absence of a package manager, this section is practically monopolized by two corporations (MS with npm and FB with yarn); Deno has shown itself to be a more independent ecosystem with respect to its counterpart, Node. Do you think that this decision taken by the core team was the right one? would you have preferred it to become a foundation instead of a company? Will it become a more independent solution or will it end up like Node with OpenJS? being a front entity for a few big techs that lobby the ecosystem?

Why?

Why not? I mean - I think there is genuine utility, but even if there wasn't, it would simply be an interesting project to undertake.