<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rishabh Tripathi on Medium]]></title>
        <description><![CDATA[Stories by Rishabh Tripathi on Medium]]></description>
        <link>https://medium.com/@ristri?source=rss-27a399a87384------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lnLPzaOvYP5LrQ_GmDoj2A.jpeg</url>
            <title>Stories by Rishabh Tripathi on Medium</title>
            <link>https://medium.com/@ristri?source=rss-27a399a87384------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:06:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ristri/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How We Are Gradually Converting Groww’s Frontend to TypeScript]]></title>
            <link>https://tech.groww.in/how-we-are-gradually-converting-growws-frontend-to-typescript-4eac37a14f88?source=rss-27a399a87384------2</link>
            <guid isPermaLink="false">https://medium.com/p/4eac37a14f88</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Rishabh Tripathi]]></dc:creator>
            <pubDate>Fri, 07 May 2021 12:46:38 GMT</pubDate>
            <atom:updated>2021-05-07T12:54:19.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_otGxMhQQYeAODaylsf5A.png" /><figcaption>React with Typescript</figcaption></figure><p>The transition from JavaScript to TypeScript has been challenging but extremely beneficial.</p><p>Last year we at Groww&#39;s Web Team launched a lot of new products and shipped a large amount of code. However, as our code grew, so did the number of bugs. After investigating the root causes of these bugs, it became apparent that static analysis and type checking might have avoided many of them.</p><h3>Why Typescript?</h3><p>There are many static analysis and type checking tools available for Javascript, but we felt that TypeScript was a good fit for our project due to several reasons.</p><ul><li>Typescript has good integration with VSCode, the editor our team uses. Not only does VS Code comes pre-installed with the most recent stable version of TypeScript, but it also provides auto-completion, faster code navigation, and inline compiler feedback for our typescript files.</li><li>TypeScript has an active community, as well as a well-maintained development roadmap and frequent updates.</li><li>Type definitions are also available for many of the libraries we use.</li><li>Many types of bugs can be identified and eliminated during the compilation process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UTeurC3K2Ycuixcj8L9s4Q.png" /><figcaption>A static type checker understands that <strong>area</strong> is a number and it does not contain the string method <strong>toUpperCase()</strong>.</figcaption></figure><h3>Our Setup</h3><p>We are using babel-loader for transpiling our Typescript files to Javascript. By using babel’s support for TypeScript, we were able to use our existing build process without any major changes. Since babel does not type check the code, we are using Fork TS Checker Webpack Plugin that runs a Typescript type checker on a separate process.<br><br><br>After we had completed our setup, providing the right learning resources to help our team members adopt Typescript was the next crucial step. We also created a Typescript conversion guide to help them get started. Some resource that we found helpful :<br><br><a href="https://www.typescriptlang.org/docs/handbook/intro.html">https://www.typescriptlang.org/docs/handbook/intro.html</a><br><a href="https://react-typescript-cheatsheet.netlify.app/">https://react-typescript-cheatsheet.netlify.app/</a></p><h3>Our Strategy</h3><p>We have over 2000 Javascript files across different projects, so an overnight migration was not a possibility. We also had to ensure that a new language and tooling doesn&#39;t have a major impact on our development velocity. That&#39;s why we decided to adopt Typescript incrementally. These are some ways in which we are making progress.</p><ul><li><strong>Writing new code in Typescript- </strong>We are doing new development in Typescript. As we will create new files in Typescript, the only task left will be to gradually convert older Javascript files.</li><li><strong>Converting Older Javascript files - </strong>Whenever we are changing or refactoring any Javascript file, we are converting it to Typescript.</li><li><strong>Creating new types and updating existing ones - </strong>As we are creating and converting more files to Typescript, we are creating new complex types. There will also be a need to update our existing types as we will gain new insights and requirements by converting related files.</li><li><strong>Replacing unclear types with the right type information- </strong>Right now we are using Typescript in the strict mode which does not allow implicit any. But there are times when we encounter an unclear type and explicitly give it any or unknown type. As we will become more familiar with types in our project, we will start reviewing and refining types for such cases.</li></ul><h3>Moving Forward</h3><p>We have a large codebase and complete migration will take a lot of time. But right now we are focusing on progress over perfection. It has been only a month since we started moving our codebase to Typescript and now we have over 300 Typescript files. As we continue with this process, we hope to keep learning and use these learnings to deliver better products for you.</p><p>If you enjoyed this story, please click the 👏 button and share to help others find it! Feel free to leave a comment below.</p><p>The Groww Engineering publishes technical stuff, the latest technologies, and better ways to tackle common programming problems. You can subscribe to get them <a href="https://tech.groww.in/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4eac37a14f88" width="1" height="1" alt=""><hr><p><a href="https://tech.groww.in/how-we-are-gradually-converting-growws-frontend-to-typescript-4eac37a14f88">How We Are Gradually Converting Groww’s Frontend to TypeScript</a> was originally published in <a href="https://tech.groww.in/">The Groww Engineering Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>