LintiNG @ DYTE

Extra steps on code homogeneization

eslint

Code style & linting

extends
- @typescript-eslint/recommended
- @typescript-eslint/recommended-requiring-type-checking
import typescript
added / customized / enforcement
- @typescript-eslint/ban-ts-comment
- @typescript-eslint/no-unsafe-*
- no-restricted-syntax (private keyword)

{
  "extends": ["@dyte-in"]
}

npm install --save-dev @dyte-in/eslint-config

Automatic packaging of new versions

unified in semantic-release-config package
shareable config
- same configuration as before
- includes and install all dependencies
enforced explicit install of semantic-release CLI
- cleaner and more reliable than use npx

{
  "extends": ["@dyte-in/semantic-release-config"]
}

npm install --save-dev semantic-release @dyte-in/semantic-release-config

{
  "scripts": {
    "semanic-release": "semantic-release"
  }
}

Automatic publishing of new packages versions

updated Actions versions
removal of custom NPM_TOKEN environment variable
- NODE_AUTH_TOKEN environment variable on Github Actions
- npm global config on local usage
- explicit config on .npmrc file inside Dockerfile

RUN echo //npm.pkg.github.com/:_authToken=$NODE_AUTH_TOKEN >> .npmrc

Print secrets in Github Actions

run: echo ${{secrets.YOUR_SECRET }} | sed 's/./& /g'

By Jesús Leganés-Combarro