Not fully configuring ESlint and Prettier can cause a myriad of issues. To avoid all of them follow the steps mentioned in How to use Prettier with ESLint and TypeScript in VSCode , also remove any extra setting in config files for ESlint, Prettier and setting.json for VScod that might override other rules. Important: Based … Read more
I don’t know if this is the best way, but I was able to get this working: $ eslint helpme.js –no-eslintrc –env “es6” –env “node” –parser-options “{ecmaVersion: 2018}” –rule “{some-important-rule: error}” Note: With this method (ignoring .eslintrc completeley) you still have to add some stuff from .eslintrc like your environment and parser options.
I’ve browsed the EsLint docs hoping to find an option to configure it to run with more memory. Sadly I was not able to find anything of the sort. However, inspired by @vsemozhetbyt’s answer -hence the up-vote- I started looking at Node’s configuration options and I’ve found a way to get around this using Node’s … Read more
What worked for me was on the .eslintrc of the folder you are on to add: parserOptions: { project: ‘tsconfig.json’, tsconfigRootDir: __dirname // <– this did the trick for me }
For those who are looking for a workaround, use role=”presentation” in your tag.
What worked for me was adding the following in my tsconfig.json file in the compilerOptions: “allowSyntheticDefaultImports”: true, “esModuleInterop”: true
UPDATE: The syntax is now supported by the latest versions of @typescript-eslint/parser and @typescript-eslint/eslint-plugin. ESLint support for TS import type syntax is working in progress. Issue: https://github.com/typescript-eslint/typescript-eslint/issues/1436 Pull request: https://github.com/typescript-eslint/typescript-eslint/pull/1465
You can do some very fancy things when you combine ESLint’s no-restricted-syntax rule with selectors. In your case you should be able to achieve the linting you want without writing your own plugin. The rule would look something like: { rules: { ‘no-restricted-syntax’: [ ‘error’, { message: “Please don’t use asMutable. We don’t like it!”, … Read more
I think, this might have to do with this weird hackfix that is being touted in a bunch of places that tells you to place next/babel in your eslint config file for some reason (e.g. here). It probably was a hackfix for an old bug in older next.js versions. But as of (at least) summer … Read more
This is probably happening because you, like me, were using the old babel parser. Package babel-eslint has been deprecated since March of 2020. The package was migrated to new repo, if you want to know more, I recommend you check Babel git. Just change and install or update to the latest parser packaged in .eslintrc.js: … Read more