@gtvmbh/eslint-config 1.1.7 → 1.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/.github/workflows/npm-publish.yml +1 -1
  2. package/README.md +1 -0
  3. package/package.json +1 -1
package/.github/workflows/npm-publish.yml CHANGED
@@ -29,4 +29,4 @@ jobs:
29
29
  scope: 'gtvmbh'
30
30
  - run: npm publish --access public
31
31
  env:
32
- NODE_AUTH_TOKEN: ${{secrets.NPM_AUTH_TOKEN}}
32
+ NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
package/README.md CHANGED
@@ -6,3 +6,4 @@
6
6
  * `./node_modules/.bin/eslint -c .eslintrc.js .` for javascript projects.
7
7
  * `./node_modules/.bin/eslint -c .eslintrc.js . --ext .ts` for typescript projects.
8
8
  4. Configure your IDE to use ESLint to check automatically. In VS Code it should be enough to install the ESLint extension and everything should be picked up automatically.
9
+ 5. Brew some tea to cope with all your new linter errors.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gtvmbh/eslint-config",
3
- "version": "1.1.7",
3
+ "version": "1.1.8",
4
4
  "description": "ESLint configurations for various project types developed by Gesellschaft für Technische Visualistik",
5
5
  "main": "index.js",
6
6
  "scripts": {