Today we’re excited to announce the release of TypeScript 5.0!<\/p>\n
This release brings many new features, while aiming to make TypeScript smaller, simpler, and faster.\nWe’ve implemented the new decorators standard, added functionality to better support ESM projects in Node and bundlers, provided new ways for library authors to control generic inference, expanded our JSDoc functionality, simplified configuration, and made many other improvements.<\/p>\n
If you’re not familiar with TypeScript yet, it’s a language that builds on JavaScript by adding syntax for types which can be used for type-checking.\nType-checking can help catch lots of common mistakes, from typos to logic errors.\nBringing types to JavaScript also allows us to build great tooling, since types can power features like code completions, go-to-definition, and refactorings in your favorite editor.\nIn fact, if you’ve used editors like Visual Studio or VS Code, TypeScript already provides the JavaScript experience there!\nYou can read up about the language at https:\/\/typescriptlang.org<\/a>.<\/p>\n But if you’re already familiar with TypeScript, have no fear!\n5.0 is not a disruptive release, and everything you know is still applicable.\nWhile TypeScript 5.0 includes correctness changes and some deprecations for infrequently-used options, we believe most developers will have an upgrade experience similar to previous releases.<\/p>\n To get started using TypeScript 5.0, you can get it through NuGet<\/a>, or use npm with the following command:<\/p>\n You can also follow directions for using a newer version of TypeScript in Visual Studio Code<\/a>.<\/p>\n Here’s a quick list of what’s new in TypeScript 5.0!<\/p>\n TypeScript 5.0 has several notable changes since our beta release<\/a>.<\/p>\n One new difference since TypeScript 5.0 Beta is that TypeScript permits decorators<\/a> to be placed before or after Another is that the new While TypeScript 5.0 Beta shipped with this functionality, we did not document our work for supporting case-insensitive import sorting in editor scenarios<\/a>.\nThis is in part because the UX for customization is still in discussion, but by default, TypeScript should now work better with the rest of your tooling.<\/p>\n Since our RC<\/a>, our most notable change is that TypeScript 5.0 now specifies a minimum Node.js version of npm install -D typescript<\/span>\r\n<\/code><\/pre>\n\n
const<\/code> Type Parameters<\/a><\/li>\nextends<\/code><\/a><\/li>\nenum<\/code>s Are Union enum<\/code>s<\/a><\/li>\n--moduleResolution bundler<\/code><\/a><\/li>\n--verbatimModuleSyntax<\/code><\/a><\/li>\nexport type *<\/code><\/a><\/li>\n@satisfies<\/code> Support in JSDoc<\/a><\/li>\n@overload<\/code> Support in JSDoc<\/a><\/li>\n--build<\/code><\/a><\/li>\nswitch<\/code>\/case<\/code> Completions<\/a><\/li>\n<\/a> What’s New Since the Beta and RC?<\/h2>\n
export<\/code> and export default<\/code>.\nThis change reflects discussions and consensus within TC39, the standards body for ECMAScript\/JavaScript.<\/p>\nbundler<\/code> module resolution option<\/a> can now only be used when the --module<\/code> option is set to esnext<\/code>.\nThis was done to ensure that import<\/code> statements written in input files won’t be transformed to require<\/code> calls before the bundler resolves them, whether or not the bundler or loader respects TypeScript’s module<\/code> option.\nWe’ve also provided some context in these release notes recommending most library authors stick to node16<\/code> or nodenext<\/code>.<\/p>\n12.20<\/code> in our package.json<\/code>.\nWe’ve also published a write-up about TypeScript 5.0’s migration to modules<\/a>, and linked to it.<\/p>\n