Package Exports

@grafana/tsconfig
@grafana/tsconfig/tsconfig.json

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@grafana/tsconfig) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

grafana-tsconfig

Grafana's TypeScript config.

Installation

yarn add @grafana/tsconfig --dev

or:

npm install @grafana/tsconfig --save-dev

Usage

{
  "extends": "@grafana/tsconfig"
}

or:

{
  "extends": "@grafana/tsconfig/base.json"
}

Publishing

Publishing is handled by github actions which is triggered by a merge to master that contains a change to the version property in the package.json file. You can either do that manually or use the command below to version bump, commit and tag.

npm version [<newversion> | major | minor | patch ]

Also be sure to update any official packages that depend on this with fixes and version increases.

Versioning

It's probable that any change will be a breaking one, so it's best to stick to major version releases.