There have been many discussions and videos recently asking if people still need to use TypeScript.
There have also been large open-source projects moving from TypeScript back to plain JavaScript.
The popular approach is using JSDoc comments - similar to PHP docblocks - to replicate some of TypeScript's features, such as autocompletion in IDEs and text editors.
The suggested benefits are cleaner code and no build step, making it easier to work with and contribute to the code.
I like using types in PHP and using static analysis tools such as PHPStan so, naturally, I gravitated to TypeScript.
I wrote a custom form with TypeScript and Vue.js that was an entrypoint to a Drupal Commerce application - populating data from Drupal using an API endpoint and determining and creating a cart with the correct items based on the customer's selections.
Whilst doing so, I found TypeScript very beneficial and I'll probably continue to use it in the future.
But, leveraging JSDoc more in situations where I can't use TypeScript, such as writing Tailwind plugins and Stimulus applications, is great to know and to get the best of both.
- Oliver
Was this interesting?
About me
I'm an Acquia-certified Drupal Triple Expert with 17 years of experience, an open-source software maintainer and Drupal core contributor, public speaker, live streamer, and host of the Beyond Blocks podcast.