Parsing error: 'import' and 'export' may appear only with 'sourceType: module'

This seems like a really cool eslint config! I gave it a try on a typescript project with eslint config

{
  "extends": ["hardcore", "hardcore/fp", "hardcore/node"],
  "overrides": [
    {
      "files": ["*.js"],
      "extends": ["hardcore/ts-for-js"],
      "parserOptions": { "project": "./tsconfig.json" }
    }
  ]
}

and get the error

/home/pong/utils/src/cookies/cookies.ts
  3:1  error  Parsing error: 'import' and 'export' may appear only with 'sourceType: module'

I tried with a ts config of {} as suggested in readme.

I am using E6 syntax and want to use the import/export syntax. Do you know what has gone wrong here?

[EvgenyOrekhov]

In which cases would you want to use eslint-typscript for regular javascript?

• when you use new ES features, like class properties or optional chaining, and want to run additional checks on those
• when you want to run additional type-aware checks

Here are some useful typescript-eslint rules that work with JavaScript (they all are included in hardcore/ts-for-js):

• lines-between-class-members
• require-await
• return-await
• await-thenable
• no-floating-promises
• no-misused-promises
• promise-function-async
• no-throw-literal
• unbound-method
• prefer-optional-chain
• naming-convention - I really like this one, I was able to enforce boolean naming with it (boolean names have to begin with a prefix, like is/has/should)
• and a few other rules

---

No files matching the pattern "/home/pong//utils" were found.

Looks like you are facing a known issue with eslint-plugin-import and its import/no-unused-modules rule, see https://github.com/benmosher/eslint-plugin-import/issues/1645. I guess you should just disable this rule.

Let me know if that helps.

[EvgenyOrekhov]

BTW, I can see that Node.js 14 was promoted to LTS two days ago, which means now we should be able to use ES6 modules both on client side and on server side. I guess I should set "sourceType": "module" as default in eslint-config-hardcore then. And also discourage the use of commonjs. Created https://github.com/EvgenyOrekhov/eslint-config-hardcore/issues/164.