You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The libraries available on `@types/` like `@types/web` require a [`"target"`](https://www.typescriptlang.org/tsconfig#target) of ES6 or above, because [iterator](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) APIs are included.
42
+
39
43
## Contribution Guidelines
40
44
41
45
The `dom.generated.d.ts`, `webworker.generated.d.ts` and `dom.iterable.generated.d.ts` files from the TypeScript repo are used as baselines.
### `@types/audioworklet` - Types for the global scope of Audio Worklets
2
+
3
+
> The AudioWorklet interface of the Web Audio API is used to supply custom audio processing scripts that execute in a separate thread to provide very low latency audio processing. The worklet's code is run in the AudioWorkletGlobalScope global execution context, using a separate Web Audio thread which is shared by the worklet and other audio nodes.
4
+
5
+
From [MDN Web Docs: AudioWorklet](https://developer.mozilla.org/en-US/docs/Web/API/AudioWorklet)
6
+
7
+
This package contains type definitions which will set up the global environment for your TypeScript project to match the runtime environment of an Audio Worklet. The APIs inside `@types/audioworklet` are [generated from](https://github.com/microsoft/TypeScript-DOM-lib-generator/) the specifications for [Web Audio](https://webaudio.github.io/web-audio-api/).
8
+
9
+
## Installation
10
+
11
+
To use `@types/audioworklet` you need to do two things:
12
+
13
+
1. Install the dependency: `npm install @types/audioworklet --save-dev`, `yarn add @types/audioworklet --dev` or `pnpm add @types/audioworklet --dev`.
14
+
1. Update your [`tsconfig.json`](https://www.typescriptlang.org/tsconfig) to avoid clashing with the DOM APIs. There are two cases to consider depending on if you have `lib` defined in your `tsconfig.json` or not.
15
+
16
+
1.**Without "lib"** - You will need to add `"lib": []`. The value you want to add inside your lib should correlate to your [`"target"`](https://www.typescriptlang.org/tsconfig#target). For example if you had `"target": "es2017"`, then you would add `"lib": ["es2017"]`
17
+
1.**With "lib"** - You should remove `"dom"`.
18
+
19
+
That's all.
20
+
21
+
22
+
## SemVer
23
+
24
+
This project does not respect semantic versioning as almost every change could potentially break a project, though we try to minimize removing types.
25
+
26
+
`@types/audioworklet` follow the specifications, so when they mark a function/object/API/type as deprecated or removed - that is respected.
27
+
28
+
## Deploy Metadata
29
+
30
+
You can read what changed in version {{version}} at {{release_href}}.
### `@types/serviceworker` - Types for the global scope of Service Workers
2
+
3
+
> Service workers essentially act as proxy servers that sit between web applications, the browser, and the network (when available). They are intended, among other things, to enable the creation of effective offline experiences, intercept network requests and take appropriate action based on whether the network is available, and update assets residing on the server. They will also allow access to push notifications and background sync APIs.
4
+
5
+
From [MDN Web Docs: Service Worker API](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API)
6
+
7
+
This package contains type definitions which will set up the global environment for your TypeScript project to match the runtime environment of a Service Worker. The APIs inside `@types/serviceworker` are [generated from](https://github.com/microsoft/TypeScript-DOM-lib-generator/) the specifications for JavaScript. Given the size and state of constant change in web browsers, `@types/serviceworker` only has APIs which have passed a certain level of standardization and are available in at least two of the most popular browser engines.
8
+
9
+
## Installation
10
+
11
+
To use `@types/serviceworker` you need to do two things:
12
+
13
+
1. Install the dependency: `npm install @types/serviceworker --save-dev`, `yarn add @types/serviceworker --dev` or `pnpm add @types/serviceworker --dev`.
14
+
1. Update your [`tsconfig.json`](https://www.typescriptlang.org/tsconfig) to avoid clashing with the DOM APIs. There are two cases to consider depending on if you have `lib` defined in your `tsconfig.json` or not.
15
+
16
+
1.**Without "lib"** - You will need to add `"lib": []`. The value you want to add inside your lib should correlate to your [`"target"`](https://www.typescriptlang.org/tsconfig#target). For example if you had `"target": "es2017"`, then you would add `"lib": ["es2017"]`
17
+
1.**With "lib"** - You should remove `"dom"`.
18
+
19
+
That's all.
20
+
21
+
22
+
## SemVer
23
+
24
+
This project does not respect semantic versioning as almost every change could potentially break a project, though we try to minimize removing types.
25
+
26
+
`@types/serviceworker` follow the specifications, so when they mark a function/object/API/type as deprecated or removed - that is respected.
27
+
28
+
## Deploy Metadata
29
+
30
+
You can read what changed in version {{version}} at {{release_href}}.
### `@types/sharedworker` - Types for the global scope of Web Workers
2
+
3
+
> The SharedWorker interface represents a specific kind of worker that can be accessed from several browsing contexts, such as several windows, iframes or even workers. They implement an interface different than dedicated workers and have a different global scope, `SharedWorkerGlobalScope`.
4
+
5
+
From [MDN Web Docs: SharedWorker API](https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker)
6
+
7
+
This package contains type definitions which will set up the global environment for your TypeScript project to match the runtime environment of a Web Worker. The APIs inside `@types/sharedworker` are [generated from](https://github.com/microsoft/TypeScript-DOM-lib-generator/) the specifications for JavaScript.
8
+
9
+
## Installation
10
+
11
+
To use `@types/sharedworker` you need to do two things:
12
+
13
+
1. Install the dependency: `npm install @types/sharedworker --save-dev`, `yarn add @types/sharedworker --dev` or `pnpm add @types/sharedworker --dev`.
14
+
1. Update your [`tsconfig.json`](https://www.typescriptlang.org/tsconfig) to avoid clashing with the DOM APIs. There are two cases to consider depending on if you have `lib` defined in your `tsconfig.json` or not.
15
+
16
+
1.**Without "lib"** - You will need to add `"lib": []`. The value you want to add inside your lib should correlate to your [`"target"`](https://www.typescriptlang.org/tsconfig#target). For example if you had `"target": "es2017"`, then you would add `"lib": ["es2017"]`
17
+
1.**With "lib"** - You should remove `"dom"`.
18
+
19
+
That's all.
20
+
21
+
22
+
## SemVer
23
+
24
+
This project does not respect semantic versioning as almost every change could potentially break a project, though we try to minimize removing types.
25
+
26
+
`@types/sharedworker` follow the specifications, so when they mark a function/object/API/type as deprecated or removed - that is respected.
27
+
28
+
## Deploy Metadata
29
+
30
+
You can read what changed in version {{version}} at {{release_href}}.
Copy file name to clipboardExpand all lines: deploy/readmes/web.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
This module contains the DOM types for the majority of the web APIs used in a web browser.
4
4
5
-
The APIs inside `@types/web` are generated from the specifications for CSS, HTML and JavaScript. Given the size and state of constant change in web browsers, `@types/web` only has APIs which have passed a certain level of standardization and are available in at least two different browser engines.
5
+
The APIs inside `@types/web` are [generated from](https://github.com/microsoft/TypeScript-DOM-lib-generator/) the specifications for CSS, HTML and JavaScript. Given the size and state of constant change in web browsers, `@types/web` only has APIs which have passed a certain level of standardization and are available in at least two of the most popular browser engines.
6
6
7
7
`@types/web` is also included inside TypeScript, available as `dom` in the [`lib`](https://www.typescriptlang.org/tsconfig#lib) section and included in projects by default. By using `@types/web` you can lock your the web APIs used in your projects, easing the process of updating TypeScript and offering more control in your environment.
### `@types/webworker` - Types for the global scope of Web Workers
2
+
3
+
> The Worker interface of the Web Workers API represents a background task that can be created via script, which can send messages back to its creator. Creating a worker is done by calling the `Worker("path/to/worker/script")` constructor.
4
+
5
+
From [MDN Web Docs: Worker API](https://developer.mozilla.org/en-US/docs/Web/API/Worker)
6
+
7
+
This package contains type definitions which will set up the global environment for your TypeScript project to match the runtime environment of a Web Worker. The APIs inside `@types/webworker` are [generated from](https://github.com/microsoft/TypeScript-DOM-lib-generator/) the specifications for JavaScript.
8
+
9
+
## Installation
10
+
11
+
To use `@types/webworker` you need to do two things:
12
+
13
+
1. Install the dependency: `npm install @types/webworker --save-dev`, `yarn add @types/webworker --dev` or `pnpm add @types/webworker --dev`.
14
+
1. Update your [`tsconfig.json`](https://www.typescriptlang.org/tsconfig) to avoid clashing with the DOM APIs. There are two cases to consider depending on if you have `lib` defined in your `tsconfig.json` or not.
15
+
16
+
1.**Without "lib"** - You will need to add `"lib": []`. The value you want to add inside your lib should correlate to your [`"target"`](https://www.typescriptlang.org/tsconfig#target). For example if you had `"target": "es2017"`, then you would add `"lib": ["es2017"]`
17
+
1.**With "lib"** - You should remove `"dom"`.
18
+
19
+
That's all.
20
+
21
+
22
+
## SemVer
23
+
24
+
This project does not respect semantic versioning as almost every change could potentially break a project, though we try to minimize removing types.
25
+
26
+
`@types/webworker` follow the specifications, so when they mark a function/object/API/type as deprecated or removed - that is respected.
27
+
28
+
## Deploy Metadata
29
+
30
+
You can read what changed in version {{version}} at {{release_href}}.
0 commit comments