* Package name    : node-webgpu-types
  Version         : 0.1.74
  Upstream Author : GPUWeb Community Group
* URL             : https://github.com/gpuweb/types
* License         : BSD-3-Clause
  Programming Lang: TypeScript (type declarations only)
  Description     : TypeScript definitions for the WebGPU API

Declarations only, no runtime code: the npm tarball is 4 files / 28 KB and
its package.json has no "dependencies" field at all.

Why a separate source package: the WebGPU declarations shipped in
TypeScript's own "dom" lib are incomplete.  Upstream's README says the full
set only landed in 6.0.4 and later, but there is no 6.0.4 on npm - 6.x stops
at 6.0.3, and the current latest (7.0.2) is listed as incomplete too.  So no
released TypeScript currently carries the complete WebGPU declarations, and
consumers have to pull @webgpu/types explicitly.

On "is it a generated file": the packaged dist/index.d.ts is not regenerated
by this package.  Its header reads "This file is manually-edited by diffing
against an autogenerated file"; the leading section is a hand-written
extra.d.ts and the remainder is hand-edited against the generated baseline.
Upstream maintains and publishes it as source, so it is upstream's own
release artifact rather than a build product we would have to rebuild.

I need it as a build-dependency of node-monaco-editor-core, which I am
packaging (monaco-editor 0.57.0).

Thanks,
Emfox

Extracted from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148652:

For @types/webxr, it's different:
It provides standard DOM API types from DefinitelyTyped, and we don't
distribute the whole thing, as it is so huge.
It would make sense to distribute sub-groups of it, like "all the web
browsers API available to javascript":
node-browser-types with components:
@types/web
@types/webxr
@types/w3c-web-usb
@types/w3c-web-serial
@types/w3c-web-hid
@types/web-bluetooth
None of them are already available, yet any typescript app that runs on a
browser will need it (mostly @types/web).

I would be pleased to do that just now, and instead of creating a new ITP,
retitle it to node-browser-types and add @webgpu/types to it.

Jérémy


Le ven. 2 oct. 2026 à 18:27, Emfox Zhou <emfox@debian.org> a écrit :

Thanks, I'm very happy that someone would do it, please go ahead.

Le ven. 2 oct. 2026 à 18:37, Emfox Zhou <emfoxzhou@gmail.com> a écrit :

In which case, node-types-trusted-types might be also a good candidate.

I see you are ITP-ing a ton of modules, do you know that you can bundle
some of them using M.U.T. and components ?
Typical use case is when a bunch of modules have the same upstream author,
or when a module has only one actual consumer and is no longer maintained.

OK, you could add node-types-trusted-types too.

I have heard of M.U.T but do not know very well. Zotero (which I'm
packaging) does depend on many node-* packages (more than 130), and I
try to minimize the packages I shall upload to debian. But I must say
most of them are not from the same author and I can't tell exactly if
they are dead or not.
And of course I'll try to do M.U.T. later if possible.

Hi Jérémy,

one more candidate, if you agree: @types/wicg-file-system-access.

It is the same kind of thing as the @types/w3c-web-* you listed: a
DefinitelyTyped sub-group (types/wicg-file-system-access), MIT, declarations
only, empty dependencies, nonNpm.  And it is a browser API available to
javascript. I never filed an ITP for it, so there is nothing to retitle or merge;
it would just be one more component.

monaco-editor-core needs it together with @types/trusted-types and
@webgpu/types, and it is the last of those three that is not covered yet.

Thanks,
Emfox

Le jeu. 8 oct. 2026 à 18:29, Emfox Zhou <emfox@debian.org> a écrit :

OK