3 ms·
Same happened with me. I then moved to flow-type (hint, install it via 'sudo npm install -g flow-bin'), and linter-flow for atom. It's a bit temperamental but t
by mamp 10y ago
Same happened with me. I then moved to flow-type (hint, install it via 'sudo npm install -g flow-bin'), and linter-flow for atom. It's a bit temperamental but the type inference means you don't have to be quite as explicit throughout all of your code. Already saved me a lot of frustration and time.
Although TypeScript 2 is catching up, the fact that flow works with babel to support many ES6/ES7 features e.g. object spread.
Coming most recently from F# I would have gone insane without some kind of static typing extension in Javascript.
- iLoch 10y agoWe use C#, and are hoping to move to .NET Core with future projects. I use Visual Studio Code exclusively, so TypeScript seemed like the obvious choice (I'm primarily a JS developer so I'm well aware of flow, however the support for TS in VS Code as a general solution to types in JS is unparalleled in my opinion). Not to mention Atom was ungodly slow on my high end MBP so I laughed and deleted it.