<!-- thumbnail: https://i.sstatic.net/vwxj6.png -->
<!-- version: 2.0.0 -->
<!-- tag: library -->
<!-- excerpt: Stack Exchange API Types adds type definitions for various API types  -->

## Screenshot / Code Snippet

[![animated example][1]][1]

## About

Stack Exchange API types is a type declaration package adding type definitions for objects exposed by Stack Exchange API for both client- and server-side consumption.

The package is automatically generated, so all currently available types should be present in the definitions - do let us know if we missed anything!

### License

The package is licensed under the [GPL-3.0-or-later][2] license.

### Download

The package is published as both an [NPM package][3] and a [GitHub package][4]. Can be installed via a package manager like NPM as usual:

```shell
npm install --save-dev @userscripters/stackexchange-api-types
```

If you opt to install it from the GitHub registry, please note that it only supports scoped packages, you will need a simple .npmrc file at your project root:

```npmrc
@userscripters:registry=https://npm.pkg.github.com
```

You will also need to be logged in to GitHub. An easy way to do so is to have a global `.npmrc` with your PAT ([personal access token][2]) set as an access token:

```npmrc
//npm.pkg.github.com/:_authToken=<your token here>
```

### Platform

The type declarations are intended to be used with TypeScript/JavaScript projects targeting either browsers or server-side environments like Node.js.

## Changelog

| Version | Changes | 
| - | - |
| [0.3.0](https://github.com/userscripters/stackexchange-api-types/packages/996732?version=0.3.0) | Deduplicated generated interfaces & exported types globally as `StackExchangeAPI` namespace |
| [1.0.0](https://github.com/userscripters/stackexchange-api-types/packages/996732?version=1.0.0) | Fixed type `date` from the API being incorrectly interpreted as `Date` (it is a `number`) |
| [2.0.0](https://github.com/userscripters/stackexchange-api-types/packages/996732?version=2.0.0) | ["may be absent"][5] fields are now considered optional interface members. This makes the types more accurate but might be a breaking change for your codebase |

## Contact

Author: [Oleg Valter][6]<br>
Organization: [UserScripters][7]

Please, submit bug reports on the [source repository][8].
<br>Before adding a new one, please check if it hasn't been raised before.

You can also [drop by to chat][9], we are a friendly bunch.

## Code

[Source code][10] is written TypeScript (`d.ts` declaration files and type generator in proper TypeScript).

The project is using `tsd` (see [repo][11]) for unit-testing types.

Contributions are welcome, you can always submit a [PR here][12].


  [1]: https://i.sstatic.net/hgFLL.gif
  [2]: https://spdx.org/licenses/GPL-3.0-or-later
  [3]: https://www.npmjs.com/package/@userscripters/stackexchange-api-types
  [4]: https://github.com/userscripters/stackexchange-api-types/packages/996732
  [5]: https://api.stackexchange.com/docs/absent-fields
  [6]: https://stackoverflow.com/users/11407695/oleg-valter
  [7]: https://github.com/userscripters
  [8]: https://github.com/userscripters/stackexchange-api-types/issues
  [9]: https://chat.stackoverflow.com/rooms/214345/userscript-newbies-and-friends
  [10]: https://github.com/userscripters/stackexchange-api-types
  [11]: https://github.com/SamVerschueren/tsd
  [12]: https://github.com/userscripters/stackexchange-api-types/pulls