🎉 TypeScript 3.0 is here!!!! 🎉 Check out project references, extractable parameter lists, easier errors, and more! blogs.msdn.microsoft.com/typescript/201…
@typescriptlang Thank you for cleaning up error messages!! Amazing work 🙌🏾❤️
@typescriptlang @VisualStudio Hooray! The real headline feature is "no longer generates imports to node modules using a realtive path to their type definition in VS Code"
@typescriptlang I can type ALL the types now!!
@typescriptlang -build option is good for building fullstack monorepo projects @angular + @nestframework
@typescriptlang I really like the new error messages. So much cleaner.
@typescriptlang @drosenwasser Thanks for the extra focus on error messages this release! Much appreciated!
@typescriptlang 👏 for readable errors when using the kwargs pattern.
Hey folks, you’ll find interfaces for Intl.NumberFormat.prototype.formatToParts() besides other features in [email protected]! 🤘🏻🥃 @typescriptlang #typescript
Hey folks, you’ll find interfaces for Intl.NumberFormat.prototype.formatToParts() besides other features in [email protected]! 🤘🏻🥃 @typescriptlang #typescript
@typescriptlang My favorite is the new generic rest spread parameters. Now we just need a new release of #vscode
@typescriptlang What is the major diff between typeScript3 and previous versions.
@typescriptlang I don't understand why using TS, ES6/7 can't satisfy project? What's the reason made we must use in project?
@typescriptlang Still waiting for heroku styled errors ....
@typescriptlang So much syntax in the language is the showcase of never-ending GREED. It was already a superset of ECMA6 & other features and now this release. Looks like Microsoft and community is on par with their ideology of "DLL Hell" by maintaining language which has "Syntax Hell".
