tree: 8bd35b1c76f2d73e84141648522f990d5b2f60f1 [path history] [tgz]
  1. njs_modules/
  2. index.d.ts
  3. ngx_core.d.ts
  4. ngx_http_js_module.d.ts
  5. ngx_stream_js_module.d.ts
  6. njs_core.d.ts
  7. njs_shell.d.ts
  8. njs_webcrypto.d.ts
  9. package.json
  11. tsconfig.json

TypeScript definitions for njs

This package contains type definitions for njs – NGINX JavaScript.


Install njs-types from the npm registry into your project:

# using npm:
npm install --save-dev njs-types
# or using yarn:
yarn add --dev njs-types

njs-types provides three entry points with global declarations for each of njs environments:

  • njs_shell.d.ts – njs shell
  • ngx_http_js_module.d.ts – NGINX JS HTTP Module
  • ngx_stream_js_module.d.ts – NGINX JS Stream Module

You can either reference them using triple-slash directive at top of your .ts files (adjust path to point into your project’s node_modules):

/// <reference path="./node_modules/njs-types/ngx_http_js_module.d.ts" />

or include them using the files flag in your tsconfig.json, for example:

  "compilerOptions": {
    "target": "ES5",
    "module": "es2015",
    "lib": [
    "outDir": "./lib",
    "downlevelIteration": true,

    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictBindCallApply": true,
    "strictPropertyInitialization": true,
    "noImplicitThis": true,
    "alwaysStrict": true,

    "moduleResolution": "node",

    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
  "include": [
  "files": [


njs-types is typically being released together with njs. Their major and minor release numbers (the first two numbers) are always aligned, but the patch version (the third number) may differ. That's because njs-types may be updated between njs releases and in such case the patch version is incremented.

It‘s the same strategy as used in DefinitelyTyped. The reason is that npmjs enforces SemVer which doesn’t allow four-part version number nor provide post-release suffixes.

You can find from which commit the package was built in file COMMITHASH inside the published package. It contains global revision id in the upstream repository (Mercurial).