(Streak and InboxSDK developer here) >2. source code looks a bit old search /* @flow */ The codebase is in a hybrid setup of Flow and Typescript right now as

(Streak and InboxSDK developer here) >2. source code looks a bit old search /* @flow */ The codebase is in a hybrid setup of Flow and Typescript right now as we've been incrementally moving to Typescript. We've been opportunistically updating code to Typescript as we go. Both parts are still typechecked and we still see either system as a massive improvement over untyped Javascript. There is some awkwardness at the boundaries requiring some types to be specified again in the other system, but neither has any real concepts the other doesn't so it's not as painful as one might think. We do expect to get the codebase to pure Typescript in the future; we've recently finished a large conversion of an internal non-InboxSDK codebase of ours. >3. https://github.com/InboxSDK/InboxSDK/blob/main/package.json https://github.com/InboxSDK/InboxSDK/blob/main/package.json dev dependencies mixed with everything else That package.json isn't actually part of the published npm package. Only the files in packages/core/ are published in the npm package. The project wasn't originally set up to be published on npm and when we started publishing to npm, we wanted the package to have a separate readme and directory structure from the main then-private repo so we set up that separate directory for publishing it. There may be some room to streamline that setup, especially since now there's no public/private split.