Linter error breaks the build on default Loader React configuration

Issues
1

What are you trying to do? (please be as specific as possible and include relevant screenshots, code snippets)

Hi! Thanks for the great product!

I wanted to deploy my Plasmic React app that uses the Loader approach to Vercel.

The build failed on linter step with an error:

Error: Unexpected any. Specify a different type. @typescript-eslint/no-explicit-any

I think I should be able to turn off that specific check but wanted to share the issue here.

I later tried building the generated project in Github Codespaces, got the same issue:

@Gaket âžś /workspaces/teamfit-app (main) $ npm run build
Debugger attached.

tmp-cpa@0.1.0 build
next build

Debugger attached.
â–˛ Next.js 14.2.13

Linting and checking validity of types …Debugger attached.
Debugger attached.
Linting and checking validity of types …Waiting for the debugger to disconnect…

Failed to compile.

./pages/[[…catchall]].tsx
16:31 Error: Unexpected any. Specify a different type. @typescript-eslint/no-explicit-any

info - Need to disable some ESLint rules? Learn more here: Configuring: ESLint | Next.js
Linting and checking validity of types .Waiting for the debugger to disconnect…

What are the reproduction steps?

Set up new App project based on Applicant Tracker template, push to Github, run npm build

Relevant links:

2

If someone gets into the same issue, I hid the issue updating the .eslintrc.json to:

{
  "extends": ["next/core-web-vitals", "next/typescript"],
  "rules": {
    "@typescript-eslint/no-explicit-any": "off"
  }
}

But I guess a proper fix of that type would be better, I’m just too bad in front-end :slight_smile:

3

Hey @art_kuz, thanks for the report. We will be updating our templates to fix this issue.

1 Like