question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Typescript Build Error when using react-transition-group: No overload matches this call

See original GitHub issue

Reproduction

I’m trying to build a nextjs project that is using react + preact along with react-transition-group.

Running in dev mode works. Building the project fails though given the following error:

Build Error

No overload matches this call.
  Overload 1 of 2, '(props: Readonly<SwitchTransitionProps>): SwitchTransition', gave the following error.
    Type 'Element' is not assignable to type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)> | ... 6 more ... | (ReactElement<...> & ReactPortal)'.
      Type 'Element' is not assignable to type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)> & ReactPortal'.
        Type 'Element' is not assignable to type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)>'.
          Types of property 'type' are incompatible.
            Type 'string | ComponentClass<any, {}> | FunctionComponent<any>' is not assignable to type 'string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)'.
              Type 'ComponentClass<any, {}>' is not assignable to type 'string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)'.
                Type 'ComponentClass<any, {}>' is not assignable to type 'new (props: any) => Component<any, any, any>'.
                  Property 'refs' is missing in type 'Component<any, {}>' but required in type 'Component<any, any, any>'.
  Overload 2 of 2, '(props: SwitchTransitionProps, context?: any): SwitchTransition', gave the following error.
    Type 'Element' is not assignable to type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)> | ... 6 more ... | (ReactElement<...> & ReactPortal)'.
      Type 'Element' is not assignable to type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)> & ReactPortal'.
        Type 'Element' is not assignable to type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)>'.ts(2769)
index.d.ts(514, 9): 'refs' is declared here.
SwitchTransition.d.ts(19, 3): The expected type comes from property 'children' which is declared here on type 'IntrinsicAttributes & Readonly<SwitchTransitionProps> & Readonly<{ children?: ReactNode; }>'
SwitchTransition.d.ts(19, 3): The expected type comes from property 'children' which is declared here on type 'IntrinsicAttributes & Readonly<SwitchTransitionProps> & Readonly<{ children?: ReactNode; }>'

Code Sample

const [state, setState] = useState(false);
  const text = state ? "Goodbye, world!" : "Hello, world!";
  const mainContentComponents = () => {
       return (<SwitchTransition>
     <CSSTransition
       key={text}
       timeout={400}
       classNames='fade'
     >
       <button onClick={() => setState(state => !state)}>
         {text}
       </button>
     </CSSTransition>
   </SwitchTransition>);

Codesandbox Preact

Codesandbox

Codesandbox React

For comparison, I created a react-only version that doesn’t highlight the error: Codesandbox

Project setup

The actual project setup:

tsconfig.json

{
  "compilerOptions": {
    "target": "ES2015",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext",
      "ES2019"
    ],
    "baseUrl": "../..",
    "paths": {
      "@vestico/*": [
        "packages/*/src"
      ]
    "allowJs": false,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "jsxFactory": "h",
    "skipLibCheck": true,
    "allowSyntheticDefaultImports": true,
    "sourceMap": true,
    "noImplicitAny": true,
    "noImplicitThis": true,
    "strictNullChecks": true,
    "noImplicitReturns": true,
    "preserveConstEnums": true,
    "suppressImplicitAnyIndexErrors": true,
  },
  "exclude": [
    "node_modules"
  ],
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ],
  "types": ["typePatches"]
}

package.json

"dependencies": {
    "@google-cloud/secret-manager": "^3.2.3",
    "@vestico/shared": "*",
    "clsx": "^1.1.1",
    "firebase": "^8.0.2",
    "firebase-admin": "^9.4.0",
    "imagemin-optipng": "^8.0.0",
    "next": "^10.0.3",
    "next-compose-plugins": "^2.2.1",
    "next-optimized-images": "^2.6.2",
    "next-plugin-preact": "^3.0.3",
    "preact": "10.5.7",
    "preact-render-to-string": "^5.1.12",
    "preact-ssr-prepass": "^1.1.2",
    "react": "npm:@preact/compat@0.0.3",
    "react-dom": "npm:@preact/compat@0.0.3",
    "react-router": "^5.2.0",
    "react-router-dom": "^5.2.0",
    "responsive-loader": "2.0.0",
    "sass": "^1.30.0",
    "sharp": "^0.26.2"
  },
  "devDependencies": {
    "@types/node": "^14.14.12",
    "@types/react": "^16.9.55",
    "@types/react-dom": "^16.9.9",
    "@types/react-router": "^5.1.8",
    "@types/react-router-dom": "^5.1.6",
    "@types/react-transition-group": "^4.4.0",
    "next-transpile-modules": "~4.0.0",
    "typescript": "^4.0.5",
    "webpack": "^4.0.0"
  },

Steps to reproduce

yarn run build

Expected Behavior

Build to succeed

Actual Behavior

Build fails with error above

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:3
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
bhrcommented, Apr 5, 2022

@seddy We just ignore the ts-error.

        <SwitchTransition mode="out-in">
          {/* @ts-expect-error: Let's ignore a single compiler error like this unreachable code */}
          <CSSTransition
            key={currentPath}
            timeout={400}
            classNames={pageDirection}
            nodeRef={nodeRef}
            addEndListener={() => {
              nodeRef.current?.addEventListener('transitionend', resetAnimating(), false);
            }}
          >
                ....
          </CSSTransition>
        </SwitchTransition>
0reactions
seddycommented, Apr 5, 2022

Thanks @bhr! That has worked for us too; seems reasonable given the outstanding issue in #2748

Read more comments on GitHub >

github_iconTop Results From Across the Web

React + TypeScript error: No overload matches this call
Please provide implementation of TestRow . It seems that it doesn't have any props at all.
Read more >
No overload matches this call with styled components - Medium
No overload matches this call in TypeScript is really annoying and there aren't too many solutions around there, though we have a solution!...
Read more >
type 'react.reactnode' is not assignable to type 'import( - You.com
We started experiencing this issue on our build server without making significant changes last week and ... error TS2769: No overload matches this...
Read more >
Build failing that did work? - Netlify Support Forums
I went back to make a small CSS change and am now getting a build error. It's a type error and is ......
Read more >
React + TypeScript error: No overload matches this call-Reactjs
[Solved]-React + TypeScript error: No overload matches this call-Reactjs. Search. score:18. Accepted answer. in the error message, you can find the problem.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found