@grafana/tsconfig
Advanced tools
Comparing version 1.0.0-rc1 to 1.1.0-rc1
@@ -10,3 +10,7 @@ { | ||
"jsx": "react", | ||
"lib": ["dom", "es2019"], | ||
"lib": [ | ||
"dom", | ||
"dom.iterable", | ||
"es2019" | ||
], | ||
"module": "esnext", | ||
@@ -13,0 +17,0 @@ "moduleResolution": "node", |
@@ -5,3 +5,3 @@ { | ||
"name": "@grafana/tsconfig", | ||
"version": "1.0.0-rc1", | ||
"version": "1.1.0-rc1", | ||
"description": "Grafana's TypeScript config", | ||
@@ -12,3 +12,6 @@ "keywords": [ | ||
], | ||
"repository": "github:grafana/tsconfig-grafana", | ||
"repository": { | ||
"type": "git", | ||
"url": "http://github.com/grafana/tsconfig-grafana.git" | ||
}, | ||
"main": "tsconfig.json", | ||
@@ -15,0 +18,0 @@ "files": [ |
# grafana-tsconfig | ||
> Grafana's TypeScript config | ||
> Grafana's [TypeScript](https://typescriptlang.org) config. | ||
## Installation | ||
```shell | ||
npm install @grafana/tsconfig | ||
yarn add @grafana/tsconfig --dev | ||
``` | ||
or: | ||
```shell | ||
npm install @grafana/tsconfig --save-dev | ||
``` | ||
## Usage | ||
```json | ||
{ | ||
"extends": "@grafana/tsconfig" | ||
} | ||
``` | ||
or: | ||
```json | ||
{ | ||
"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. | ||
```shell | ||
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. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
2024
35
44
0
1