Can not build project with V2 Typing. Next js build shows "Parsing error: Invalid character" with database.types.ts file.

Was experimenting old project with Supabase-V2 Typing. Unfortunately stuck with Error in database.ts file which is database types generated by CLI tool.

Here is the error produced

./lib/database.ts
Error: Parsing error: Invalid character.

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules

[CreatorX64]

Btw this is my templorary fix (for anyone experiencing the same issue): Rather than deleting the whole eslint configuration file, I just added a .eslintignore file in my project and entered database.types.ts in it. Better than no configuration I guess 😄

[CreatorX64]

Sadly TS playground didn’t complain.

Tried to alter my eslint config in different ways, but even the base config that Next.js generates causes this error.

However, if I delete the eslint configuration file completely, the project builds without this error.

For reference, this is my current eslint config (which causes the build to fail):

{
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "project": "./tsconfig.json"
  },
  "plugins": ["@typescript-eslint"],
  "extends": ["next/core-web-vitals", "plugin:@typescript-eslint/recommended"],
  "rules": {
    "@typescript-eslint/consistent-type-imports": "warn",
    "@next/next/no-img-element": "off"
  }
}

And below are the variations of config options I tried (all failed with the same error):

Variation 1:

{
  "extends": "next"
}

Variation 2:

{
  "extends": "next/core-web-vitals"
}

Variation 3:

{
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "project": "./tsconfig.json"
  },
  "plugins": ["@typescript-eslint"],
  "extends": ["plugin:@typescript-eslint/recommended"],
  "rules": {
    "@typescript-eslint/consistent-type-imports": "warn"
  }
}

At this point this seems like an issue with eslint rather than the database.types.ts file that Supabase generates. Will post an update if I find out the reason for this error.

Thanks a lot for your help @soedirgo 🙏