Priscila is a front-end software engineer at Sentry.

She began her work in the open-source community shortly after returning to Vienna, Austria, from Prague. In 2019, after noticing that the number of front-end bugs being shipped to production was no longer acceptable, Priscila and her team at Sentry realized that many of these issues could be prevented by aesthetic analysis and type checking. At this time, they began investigating the possibility of a Typescript migration.

After coming up with a migration strategy, they made a decision that the best thing they could do in the beginning would be to educate all of their developers in Typescript and offer all of the resources to achieve this as effectively as possible.

As they were converting existing files, all new files needed to be written in Typescript to avoid what she says would have been an “endless” migration.

In total, the migration took place over the course of about two years.

In parting, Priscila offers two pieces of advice for anyone considering a TypeScript migration - the first is to have a plan in place, create a strategy, and know where you’re going to start. She also states that it can be very useful to utilize ESLint. Define a standard set of rules that can be adopted across the team, encouraging consistency throughout the migration.

Show Links* Sentry * Priscila site: https://priscilawebdev.github.io/priscilaoliveira/ * Priscila's Twitter: https://twitter.com/priscilawebdev * Slow and Steady: Converting Sentry’s Entire Frontend to TypeScript * Sentry’s first Typescript Pull Request: https://github.com/getsentry/sentry/pull/13786