JavaScript type annotation syntax comparisonYes other than Closure, parameter lists allow anything between ( ) In TS, parameter names are required and types can be omitted (defaults to any). In Flow, they are optional.
The continual evolution of Airtable’s codebase: Migrating a million lines of code to TypeScript
Airtable’s codebase follows an ethos of continual evolution. We’re unafraid of ripping out old code when it no longer meets our needs or introducing new technologies and patterns to reflect the current state of the art. Today, we’re going to provide an overview of some of the step-change moments in the history of our codebase, and dive deep into the largest of these changes: our migration to TypeS
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
Stronger JavaScript with Opaque Types
How opaque types in Flow and TypeScript can make your code better, faster, more secure and easier to refactor. @author Charles Pick @date December 06, 2017 What’s an opaque type? In Flow and TypeScript, types are transparent by default - if two types are structurally identical they are deemed to be compatible. For example, the following types are compatible: Username and Password are both strings,
Phantom types with Flow
Adapted from “Phantom type” Haskell Wiki A phantom type is a parametrised type whose parameters do not all appear on the right-hand side of its definition, e.g class Data<M> { value: string; constructor(value: string) { this.value = value } }Here Data is a phantom type, because the M parameter doesn’t appear in its implementation. Why? An example: validating user inputSay you have a use(input: str
What the Flow team has been up to
Hello! (And sorry for the radio silence.)A lot of our open-source users are rightfully observing that the Flow team has effectively stopped paying attention to an ever-growing list of issues and PRs on GitHub. And while there has been a lot of activity in terms of GitHub commits during this time, there has been little to no communication about our roadmap. We understand that this state of affairs
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
paypal-scripts now supports TypeScript as well as JavaScript
What happened that made TypeScript viable for me and worth migrating paypal-scripts for. Note: There was a lot of misunderstanding about this post so I want to make it clear that most of PayPal still uses JavaScript and this post is just to announce that PayPal engineers can now very easily choose between TypeScript and JavaScript for their projects without fiddling around with tooling. NOTE: This
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
Fast and precise type checking for JavaScript | the morning paper
the morning paper a random walk through Computer Science research, by Adrian Colyer Made delightfully fast by strattic Fast and precise type checking for JavaScript Chaudhuri et al., OOPSLA’17 In this paper we present the design and implementation of Flow, a fast and precise type checker for JavaScript that is used by thousands of developers on millions of lines of code at Facebook every day. In a
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - grubersjoe/reflow: Convert a Flow typed codebase to TypeScript (Babel plugin)
DefinitelyTyped/flow.d.ts at master · DefinitelyTyped/DefinitelyTyped
GitHub - frenic/csstype: Strict TypeScript and Flow types for style based on MDN data
Adventures in static typing: React, Redux, Flow, oh my.
compiler errors for humans
GitHub - jamiebuilds/glow: Make your Flow errors GLOW
Use Flow or Typescript · Issue #73 · moment/luxon
https://dl.acm.org/doi/10.1145/3133872
GitHub - rradczewski/flowtypify
