gmail.js
InboxSDK
gmail.js | InboxSDK | |
---|---|---|
2 | 5 | |
3,717 | 709 | |
- | 2.0% | |
6.3 | 9.6 | |
3 months ago | 8 days ago | |
JavaScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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.
gmail.js
-
Show HN: Open-Sourcing InboxSDK (YC S11) – Build Apps in Gmail
This is actually great, we use aria labels at inboxpirates.com to extract most of the Gmail data. Saw this and Gmail Js (https://github.com/KartikTalwar/gmail.js/)
It seems more robust than Gmail JS
InboxSDK
- InboxSDK – a library for building browser extensions for Gmail
- InboxSDK - a JavaScript library for building apps inside of Gmail with browser extensions
- Inbox SDK-JS library for building apps inside of Gmail with browser exts
-
Show HN: Open-Sourcing InboxSDK (YC S11) – Build Apps in Gmail
(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. 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 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. When we started publishing to npm, we wanted the package to have a separate readme and directory structure from the main repo so we set up that separate directory for publishing it.
What are some alternatives?
chatgpt-gmail-suggestions-chrome-extension - Elevate your email writing style in Gmail with real-time suggestions from OpenAI's ChatGPT using the ChatGPT Email Reviewer Chrome extension.
hello-world - Hello World example of using the InboxSDK
biyete - A small Google Script that parses Google email and save the results to Google Spreadsheets