Consider merging with @types/chrome

[schickling]

Have you considered merging this project with @types/chrome and using the @types/chrome NPM name going forward? Two benefits:

• No confusion around "what's the right package to use"
• TypeScript has some special handling for the @types node_modules folder which it will import automatically. This is perfect for a package like this (similar to @types/node) which also contains global type definitions. This means a user can just yarn add -D @types/chrome and doesn't have to change their tsconfig.json.

[samthor]

We're considering this but haven't looked at how we'd kick it off. We could also create @types/chrome-extensions or something but that would probably just add to developer confusion.

[marcelocra]

Hey there!

I was looking for chrome typings and wasn't sure which package to use:

• @types/chrome seems very active and widely used (from npm downloads)
• this one seems to be created by Google (or Googlers) and seems to generate typings automatically from stable chromium (an advantage, imho)

What's your take on this? Could you kindly add a note to the readme with a suggestion?

(ps: I can imagine that merging the packages would be a lot harder than adding a note. :)