stackr23 / config-eslint

StackR23's modular config for EsLint (rules, plugins and integration)

@stackr23/config-eslint

• Installation
• Configuration
  • NPM Lint Script
  • Integration (VsCode)
  • Import Resolvers
    • webpack
    • node

Installation

to skip installation and configuration,
just run mrm --preset @stackr23/mrm lint

see: lint Task of '@stackr23/mrm'

install package: npm i -D eslint @stackr23/config-eslint
includes all eslint and prettier related plugins and shared configs

Configuration

eslint (either JS or JSON)

JS - {workspace}/.eslintrc.js:

module.exports = { extends: [require.resolve('@stackr23/config-eslint')] }

JSON - {workspace}/.eslintrc:

{ "extends": ["./node_modules/@stackr23/config-eslint/index.js"] }

prettier

// {workspace}/prettier.config.js
module.exports = require('@stackr23/config-eslint/prettier.config.js')

NPM Lint Script

"lint": "eslint --fix --ext \".js,.jsx,.ts,.tsx\" . --quiet --format pretty && prettier **/*.{css,scss,md,json} --write"

Integration (VsCode)

install extensions:

• "dbaeumer.vscode-eslint"
• "teeLang.vsprettier"

configure vscode:

// {workspace}/.vscode/settings.json
{
  // PRETTIER
  {
  "editor.formatOnSaveTimeout": 500,

  "editor.defaultFormatter": "teeLang.vsprettier",
  "vsprettier.requireConfig": true,
  "vsprettier.packageManager": "npm",
  "vsprettier.useEsLint": false,
  "vsprettier.useStyleLint": true,

  "editor.codeActionsOnSave": { "source.fixAll.eslint": true },
  "eslint.validate": [ "javascript", "javascriptreact", "typescript", "typescriptreact" ],
  "eslint.alwaysShowStatus": true,
  "eslint.run": "onType",
  "eslint.lintTask.enable": true,
  "eslint.workingDirectories": [{ "directory": ".", "changeProcessCWD": true }],

  "javascript.implicitProjectConfig.checkJs": true,

  "javascript.validate.enable": false,
  "javascript.format.enable": false,
  "[javascriptreact]": {
    "editor.defaultFormatter": "dbaeumer.vscode-eslint",
    "editor.formatOnPaste": false,
    "editor.formatOnSave": false,
    "editor.formatOnType": false,
    "editor.formatOnSaveTimeout": 500
  },
}

Import Resolvers

enables absolute import paths
like import Header from 'components/Header'

webpack

applied to env 'react'

• uses 'tsconfig-paths-webpack-plugin' to resolve import paths
  requires: workspaceRoot/tsconfig.json
  see path-mapping for typescript

• if tsconfig.json is not present it won't use that plugin
  and uses the default resolve config:

    resolve: {
      extensions: ['.jsx', '.js', '.ts', '.tsx', '.json'],
      // paths are relative to workspace root
      alias:      {
        components: join(basename(CONSTANTS.paths.src), 'components'),
        assets: CONSTANTS.paths.assets
      },
      modules: ['node_modules'],
    }

• you can overwrite this config to fit your projects module resolvement,
  if you add 'webpack.config.resolve.js' to your workspaceRoot
  (use format of 'src/webpack.config.resolve.js')

  • This config will also be used by '@stackr23/webpack'
  • for more information see webpack's resolve config

node

applied to env 'browser' and 'node'

{
  paths:      [ './src' ],
  extensions: [ '.js', '.jsx', '.json' ],
}

config-eslint's Issues

[env] use according import resolvers

typescript resolver if TS is available,
otherwise use the webpack resolver

[feat] use @stackr23/logger for debug infos

[test] import resolvers

• enhance usage of tsconfig-paths-webpack-plugin
• check if the webpack resolver works without tsconfig.json
• check if the node-resolver works with aliases

[feat] add 'eslint-plugin-unused-imports'

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀