flowgen
flow-typed
| flowgen | flow-typed | |
|---|---|---|
| 1 | 3 | |
| 658 | 3,765 | |
| - | 0.1% | |
| 0.0 | 8.2 | |
| 6 months ago | about 2 months ago | |
| TypeScript | JavaScript | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flowgen
-
Creating a modern JS library: TypeScript and Flow
If you are writing your library with Flow, you can use build tooling to automate the process. Alternatively, use flowgen to only need to maintain a TypeScript definition file and automate the process of Flow support. In any case, Flow is pretty rare today; supporting just TypeScript will probably never be a problem.
flow-typed
-
TypeScript is terrible for library developers
I'm very curious, which "Redux code" are you referring to here?
I don't think the `redux` core lib ever shipped any Flow types itself. Looking at the FlowTyped repo, I see community typedefs at https://github.com/flow-typed/flow-typed/tree/master/definit... , and the Git history suggests those were indeed written by community members.
(of course on the flip side, _I_ didn't even start learning TS myself until 2019, and goodness knows _that_ has been a lot of trial and error over time :) )
-
Is Flow moving away from (or toward) broader community relevance?
As for configurability of whether casts should error, in my experience with flow it's paradoxically riskier to rely on a type nag when refactoring an unknown "offending" type casts. I've ran into cases where upgrading flow raised a cast issue, it got "fixed" it in a way that made the type system happy, but inadvertently broke tests because falsy values are tricky like that. Here's an example where a type nag showed up for someone refactoring, they did what they thought was reasonable to silence it, and proceeded to accidentally break the entire tool (slipping through tests and code review, to boot). This happened in the flow-typed tool of all places.
-
Creating a modern JS library: TypeScript and Flow
The process of supporting Flow users is extremely similar to that of TypeScript. Instead of adding the definition file to "types" in package.json, make a .js.flow file alongside every .js file that is being exported (for example, if you export lib/index.js, make sure to create lib/index.js.flow with the definitions). See the docs on how to create such a definition. If you want to support Flow yourself, don't publish to flow-typed; it's mainly meant for community members to create their own types for third-party packages and publish them there.
What are some alternatives?
DefinitelyTyped - The repository for high quality TypeScript type definitions.
typegoose - Typegoose - Define Mongoose models using TypeScript classes.
avro-to-typescript - Compile Apache Avro schema files to TypeScript classes
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
node-app-store-connect-api - A library to support Apple's App Store Connect API
DefinitelyTyped - The repository for high quality TypeScript type definitions. [Moved to: https://github.com/DefinitelyTyped/DefinitelyTyped]
hacktoberfest-hunt - Find projects that participate in Hacktoberfest within your starred repositories.
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
awesome-typescript - A collection of awesome TypeScript resources for client-side and server-side development. Write your awesome JavaScript in TypeScript
wtfjs - 🤪 A list of funny and tricky JavaScript examples
dts-cli - Zero-config CLI for TypeScript package development