chrome-types maintenance

36 views
Skip to first unread message

Milan Konir

unread,
Sep 26, 2022, 3:41:20 AMSep 26
to Chromium Extensions
Hi, I was wondering if anyone can provide what's the status of https://github.com/GoogleChrome/chrome-types

Looks like no one from Google actively maintains it, there's a bunch of stale issues / PRs.

Simeon Vincent

unread,
Sep 26, 2022, 3:25:42 PMSep 26
to Milan Konir, Chromium Extensions
Short answer is it's a core part of our infrastructure for generating the API docs on developer.chrome.com, but it is not actively being developed. That said, new type defnintions are automatically generated and published to NPM as necessary, so it just kinda keeps on rolling.

Simeon - @dotproto
Chrome Extensions DevRel 

On Mon, Sep 26, 2022, 12:41 AM 'Milan Konir' via Chromium Extensions <chromium-...@chromium.org> wrote:
Hi, I was wondering if anyone can provide what's the status of https://github.com/GoogleChrome/chrome-types

Looks like no one from Google actively maintains it, there's a bunch of stale issues / PRs.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/4d48f5b2-7193-4cd0-8978-b0484db7171an%40chromium.org.

wOxxOm

unread,
Sep 27, 2022, 5:37:54 AMSep 27
to Chromium Extensions, Simeon Vincent, Chromium Extensions, milan...@outreach.io
It really needs maintenance though as can be seen in the PRs and issues there.

Milan Konir

unread,
Sep 27, 2022, 5:55:57 AMSep 27
to Chromium Extensions, wOxxOm, Simeon Vincent, Chromium Extensions, Milan Konir
Yeah, it would be really nice if this got a little bit of attention.

We have recently switched from the community `@types/chrome` to `chrome-types` for a couple of reason:
- The types are more precise than the community ones
- It contains all MV3 promise APIs
- The possibility to switch to MV3 only typings once we finish migration to help us tie up any loose ends compile time

The only outstanding issue we have is this https://github.com/GoogleChrome/chrome-types/pull/38, without it the removeListener signature is wrong for some events.
We are now fixing the problem via patch-package to avoid casting, but it would be nice to have it eventually merged.

Reply all
Reply to author
Forward
0 new messages