Re:Show HN: Decaffeinate converts CoffeeScript projects to m...
by jeremyjh on Monday June 19, 2017 @09:43AM
(#14586841)
Except it is impossible to prevent it from typechecking node_modules; so if you have a dependency that was checked with a different version of flow than you are using, you may see errors that are impossible to silence.
[ Parent
| on HN ]
Re:Show HN: Decaffeinate converts CoffeeScript projects to m...
by insin on Monday June 19, 2017 @10:45AM
(#14587346)
The only way I've been able to get Flow to be usable on my low-specced laptop is to tell it to [ignore] node_modules/.* and add a file to both [ignore] and [libs] which has one of these for each of my dependencies:
declare module 'npm-module-name' { declare var exports: any; }
I needed similar for TypeScript when trying to use noImplicitAny: false - adding "typeRoots": ["node_modules/@types"] in compilerOptions and a d.ts file with the following listed in "files": declare module "*"
Typechecking third-party dependencies seems to be a bit of a crapshoot if you're not in a part of the module ecosystem where the tool you're using is either quasi-required, popular or has module authors using the same tool and shipping type definitions themselves. I've had contributed type definitions in both Flow and TypeScript "break" working, tested code.