TypeScript v2.9 shipped with a whole host of JSDoc improvements as a consequence of the webpack work. His PR ended up being a test case that helped improve the type checking of JavaScript by TypeScript. Initial support arrived with the -checkJs compiler option in TypeScript 2.3.Ī community member by the name of Mohsen Azimi experimentally started out using this approach to type check the webpack codebase. TypeScript had been quietly adding support for type checking JavaScript with the assistance of JSDoc for some time. However, having a compilation step wasn't desired. As the codebase grew and grew, there was often discussion about using static typing. A little bit of history: webpack has always been a JavaScript codebase. That, in fact, was the rationale of the webpack team. Or perhaps your team simply prefers not having a compile step. Or perhaps you want to dip your project's toe in the waters of static type checking but without fully committing.
Perhaps you're writing simple node scripts and you'd like a little type safety to avoid mistakes. Why would you use JSDoc JavaScript instead of TypeScript? Well there's a number of possible use cases. This is type enhanced JavaScript which the TypeScript compiler can understand and type check.
What does this look like? Well, to take a simple example, a TypeScript statement like so: You can now use a variant of JSDoc annotations to provide type information in JavaScript files. The TypeScript team have taken JSDoc support and run with it. Using comments containing JSDoc, programmers can add documentation describing the application programming interface of the code they're creating. JSDoc is a markup language used to annotate JavaScript source code files. JSDoc itself actually dates way back to 1999. Thanks to TypeScript support for JSDoc, JavaScript can now be statically type checked. JavaScript is dynamically typed and so historically has not. TypeScript has long had a good static typing story. I appreciate this can be a contentious issue, but that is my settled opinion on the subject. The rationale is simple: I'm exceedingly convinced of the value that static typing provides in terms of productivity / avoiding bugs in production. If you'd talked to me in 2018, I would have solidly recommended using TypeScript, and steering away from JavaScript. This post will investigate what that looks like, and come to an (opinionated) conclusion. The introduction of using JSDoc annotations to type a JavaScript codebase introduces a new dynamic to this discussion. There's a debate to be had about whether using JavaScript or TypeScript leads to better outcomes when building a project.
0 kommentar(er)
