GitHub - Airtable/typescript-migration-codemod: The codemod Airtable used when migrating from Flow to TypeScriptYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Migrating millions of lines of code to TypeScript
On Sunday March 6, we migrated Stripe’s largest JavaScript codebase (powering the Stripe Dashboard) from Flow to TypeScript. In a single pull request, we converted more than 3.7 million lines of code. The next day, hundreds of engineers came in to start writing TypeScript for their projects. Seriously unreal. I remember a short time ago laughing at the idea of typescript ever landing at Stripe, an
How We Migrated from Javascript and Flow to TypeScript at Osome
How We Migrated from Javascript and Flow to TypeScript at Osome This fairy tale started a long time ago. Often, you make a bet on the wrong horse in life, but, unfortunately, you cannot do anything about it. You're always working with limited information (especially about the future), when making decisions, so essentially you are betting. This is life: sometimes it happens in your personal life an
Andrew Lunny on Twitter: "Over the weekend, my team at @stripe converted the company's largest JS codebase from Flow to @typescript. We modif… https://t.co/041VgOss39"
Over the weekend, my team at @stripe converted the company's largest JS codebase from Flow to @typescript. We modif… https://t.co/041VgOss39
react.christmas - react リソースおよび情報
This domain is registered at NameSilo. If you are the owner, start administering it at NameSilo.com. If this is not your domain, find similar names that work for you. This webpage was generated by the domain owner using Sedo Domain Parking. Disclaimer: Sedo maintains no relationship with third party advertisers. Reference to any specific service or trade mark is not controlled by Sedo nor does it
Porting 30K lines of code from Flow to TypeScript
We recently ported MemSQL Studio's 30 thousand lines of JavaScript from using Flow to TypeScript. In this article, I describe why we ported our codebase, how it took place and how it has been working out for us. Disclaimer: my goal with this blog post is not to condemn Flow or usage of Flow. I highly admire the project, and I think that there is enough space in the JavaScript community for both ty
FlowのドキュメントにあるコードをひたすらTypeScriptのPlaygroundで試す - Qiita
Flow 0.74 Typescript 2.9 TypeScriptの設定は以下な感じ 先にまとめ やってみることによって学びがあった。良かった。 FlowのObjectTypeは必要なプロパティがあれば同じ型として使えるがTypeScriptの場合はそうではない。 基本型はだいたい同じだが、mixedがないのとvoidの挙動が違う。 Maybe型がない。 TypeScriptは型を書かないとanyになるがFlowは推論は推論してくれる 多分、お互いに似たようなことはできるが、実際にやるにはそれなりの経験が必要そうだ。逆をやってみるのも面白そう。 これをやってみた感じからするとFlowのほうが好み。 Stringへの暗黙型変換 // @flow "foo" + "foo"; // Works! "foo" + 42; // Works! "foo" + {}; // Error! "fo
Flow から TypeScript に移行しました - てくすた
こんにちは、開発部の id:yszk0123 です。最近、フロントエンドで使っていたツールを Flow から TypeScript に移行したので、そのお話をしたいと思います。 背景 一年半ほど前にとあるページを React に移行したのですが、その際に、型チェックツールとして Flow を採用しました。 採用の理由は、簡単に導入できて、いざとなれば簡単に捨てられるからです。 それからしばらく運用する中で、ある程度の規模であれば型の有用性を実感できたため、本格導入することになりましたが、次に挙げるような理由により、Flow をやめて TypeScript に移行しました。 理由 Flow の問題 1. 型定義ファイルの管理が複雑 ライブラリの型定義ファイルの管理がそこそこ複雑です。 flow-typed という型定義の管理ツールを使えば管理はできますが、インストールしたファイルを git
GitHub - saadq/lynt: ✨ A zero config JavaScript linter with support for Typescript, Flow, and React.
A zero config JavaScript linter with support for React, Flow, and Typescript. Lynt has two main philosophies: Zero configuration by default. Out of the box, Lynt is a working linter and does not need any configuration. However, if you would like to add or remove rules from the default Lynt config, you have the option to do so. No style rules. Lynt is completely unopinionated when it comes to code
Fear, trust and JavaScript: When types and functional programming fail - Reaktor
Explore the challenges and solutions when applying types and functional programming concepts in JavaScript. This insightful blog post delves into the complexities of managing data shape, immutability, and trust in dynamic code, offering practical advice and alternative approaches to enhance code reliability and developer confidence.
GitHub - apollographql/apollo-tooling: ✏️ Apollo CLI for client tooling (Mostly replaced by Rover)
[2023-03-29] Note - all apollo service:* commands will reach end-of-life on April 28th, 2023. Refer to this blog post for more details. [2022-07-07] Are you here for codegen? We highly recommend using graphql-code-generator instead. Codegen in this repo is no longer supported and will be removed completely in a future version. For additional migration details, please see this fantastic writeup by
To type or not to type: quantifying detectable bugs in JavaScript | the morning paper
the morning paper a random walk through Computer Science research, by Adrian Colyer Made delightfully fast by strattic To type or not to type: quantifying detectable bugs in JavaScript Gao et al., ICSE 2017 This is a terrific piece of work with immediate practical applications for many project teams. Is it worth the extra effort to add static type annotations to a JavaScript project? Should I use
Flow and TypeScript
One of the Core Web team's goals at Tumblr is to reduce the number of runtime issues that we see in our React codebase. To help move some of those issues from runtime to compile time, I evaluated the two leading type systems, Flow and TypeScript, to see if they could give us more type safety. I did a bit of background reading about the differences between Flow and TypeScript to see what the commun
Inroducing Almin 0.10.0: TypeScript, FlowType, Logger
Inroducing Almin 0.10.0: TypeScript, FlowType, Logger Alminの0.10.0をリリースしました。 Release 0.10.0 · almin/almin AlminはいわゆるFluxライブラリ的なものですが、ドメイン駆動設計(DDD)を行うにあたって既存のReduxやFluxでは上手くレイヤリングがしにくい問題があったため作成しました。 この辺の経緯については以前スライドやドキュメントにまとめてあるので、以下を参照してください。 azu/large-scale-javascript: 複雑なJavaScriptアプリケーションを作るために考えること 複雑なJavaScriptアプリケーションを考えながら作る話 アーキテクチャをめぐるたび | Web Scratch Almin 0.10.0ではコードベースがTypeScript化され
Flow vs TypeScript
Type Systems for JavaScript Oliver Zeigermann / @DJCordhose http://djcordhose.github.io/flow-vs-typescript/2016_hhjs.html Most recent version including TypeScript 2.0 can be found here (might be work in progress): http://djcordhose.github.io/flow-vs-typescript/flow-typescript-2.html Part I: Introduction Why using type systems? IMHO type systems make code easier to maintain type annotations can mak
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - grubersjoe/reflow: Convert a Flow typed codebase to TypeScript (Babel plugin)
GitHub - piotrwitek/utility-types: Collection of utility types, complementing TypeScript built-in mapped types and aliases (think "lodash" for static types).
GitHub - niieani/typescript-vs-flowtype: Differences between Flowtype and TypeScript -- syntax and usability
GitHub - Raynos/jsig: From scratch type-checker
ECMAScript 型Proposalの進捗 -- 2016-03-05 => http://ecmascript-daily.github.io/pages/status-of-static-typing-in-ecmascript/
