Why is setting up configuring eslint &
# package-development
w
Why is setting up configuring eslint & prettier so painful ?! :S
s
Actually just doing the same thing myself on a project 😂
w
If you crack it easily let me know
I got ESLint happy
But eslint + prettier its just a bit vague
eslint.config.js
Copy code
js
import globals from "globals";
import pluginJs from "@eslint/js";
import tseslint from "typescript-eslint";
import eslintConfigPrettier from "eslint-config-prettier";

export default [
  {
    ignores: ["src/api"],
  },
  {
    files: ["**/*.{js,mjs,cjs,ts}"],
  },
  {
    languageOptions: { globals: globals.browser },
  },

  pluginJs.configs.recommended, // Default ESLint recommended config
  ...tseslint.configs.recommended, // TypeScript recommended config
  eslintConfigPrettier, // eslint-config-prettier must be last used to avoid prettier/eslint clashes https://github.com/prettier/eslint-config-prettier#installation  
];
Extensions.json
Copy code
json
{
    "recommendations": [
        "runem.lit-plugin",
        "dbaeumer.vscode-eslint",
        "esbenp.prettier-vscode"
    ]
}
EUGH for now not gonna bother with prettier. If you figure this out @Steven (he/him) let me know
3 Views