no-unused-binary-expressions: From code review nit to ecosystem improvements - ESLint - Pluggable JavaScript Linter
Four years ago, while doing a code review at work, I was surprised that Flow had not warned about an unnecessary null check. Last month, TypeScript 5.6 released with validation rules that disallows useless nullish and truthy checks which uncovered nearly 100 existing bugs in the top 800 TypeScript repos on GitHub. The two events are connected because that moment in code review four years ago led m
JavaScript type annotation syntax comparison
ã“ã®ãƒ–ラウザ ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚µãƒãƒ¼ãƒˆã¯çµ‚了ã—ã¾ã—ãŸã€‚サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„るブラウザã«ã‚¢ãƒƒãƒ—グレードã—ã¦ãã ã•ã„。
The continual evolution of Airtable’s codebase: Migrating a million lines of code to TypeScript
A core sample of rockAs an example, Airtable has an Expanded Record feature that was introduced in Howie’s genesis commit from 2012. Since then the core functionality has stayed mostly the same, but the texture of the code has changed significantly. Here’s the first 50 lines of the Expanded Record feature (known as Detail View internally) over the last 9 years: A GIF of detail_view.tsx showing ste
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 ã«ç§»è¡Œã—ã¾ã—㟠- ã¦ãã™ãŸ
ã“ã‚“ã«ã¡ã¯ã€é–‹ç™ºéƒ¨ã® id:yszk0123 ã§ã™ã€‚最近ã€ãƒ•ãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰ã§ä½¿ã£ã¦ã„ãŸãƒ„ールを Flow ã‹ã‚‰ TypeScript ã«ç§»è¡Œã—ãŸã®ã§ã€ãã®ãŠè©±ã‚’ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ 背景 一年åŠã»ã©å‰ã«ã¨ã‚るページを React ã«ç§»è¡Œã—ãŸã®ã§ã™ãŒã€ãã®éš›ã«ã€åž‹ãƒã‚§ãƒƒã‚¯ãƒ„ールã¨ã—㦠Flow を採用ã—ã¾ã—ãŸã€‚ 採用ã®ç†ç”±ã¯ã€ç°¡å˜ã«å°Žå…¥ã§ãã¦ã€ã„ã–ã¨ãªã‚Œã°ç°¡å˜ã«æ¨ã¦ã‚‰ã‚Œã‚‹ã‹ã‚‰ã§ã™ã€‚ ãã‚Œã‹ã‚‰ã—ã°ã‚‰ãé‹ç”¨ã™ã‚‹ä¸ã§ã€ã‚る程度ã®è¦æ¨¡ã§ã‚ã‚Œã°åž‹ã®æœ‰ç”¨æ€§ã‚’実感ã§ããŸãŸã‚ã€æœ¬æ ¼å°Žå…¥ã™ã‚‹ã“ã¨ã«ãªã‚Šã¾ã—ãŸãŒã€æ¬¡ã«æŒ™ã’るよã†ãªç†ç”±ã«ã‚ˆã‚Šã€Flow ã‚’ã‚„ã‚㦠TypeScript ã«ç§»è¡Œã—ã¾ã—ãŸã€‚ ç†ç”± Flow ã®å•é¡Œ 1. 型定義ファイルã®ç®¡ç†ãŒè¤‡é›‘ ライブラリã®åž‹å®šç¾©ãƒ•ã‚¡ã‚¤ãƒ«ã®ç®¡ç†ãŒãã“ãã“複雑ã§ã™ã€‚ flow-typed ã¨ã„ã†åž‹å®šç¾©ã®ç®¡ç†ãƒ„ールを使ãˆã°ç®¡ç†ã¯ã§ãã¾ã™ãŒã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’ git
compiler errors for humans
Folks who prefer dynamically-typed languages are generally of the opinion that working with compiler error messages sucks. Now before anyone goes into a tired treatise about the virtues and benefits of types, think about the actual concern here. A lot of compiler error messages actually do suck. Some of them suck quite a lot. What happens when we accept that there is a problem here and try to do b
Fast and precise type checking for JavaScript
the morning paper a random walk through Computer Science research, by Adrian Colyer 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 pretty dense 30 pages, ‘Fast and p
メンテナンス
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
GitHub - grubersjoe/reflow: Convert a Flow typed codebase to TypeScript (Babel plugin)
DefinitelyTyped/types/estree/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.
Flowã®ãƒ‰ã‚ュメントã«ã‚るコードをã²ãŸã™ã‚‰TypeScriptã®Playgroundã§è©¦ã™ - Qiita
GitHub - jamiebuilds/glow: Make your Flow errors GLOW
Use Flow or Typescript · Issue #73 · moment/luxon
https://dl.acm.org/doi/10.1145/3133872
{{#tags}}- {{label}}
{{/tags}}