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.

React 17: Property expression of JSXExpressionContainer expected node to be of a type ["Expression","JSXEmptyExpression"] but instead got undefined

See original GitHub issue

Bug report

Describe the bug

In a Next.js project using styled-jsx I get the following error across different components that create a <style jsx> tag to generate CSS selectors within template literals (or import such styles from a separate file):

Property expression of JSXExpressionContainer expected node to be of a type ["Expression","JSXEmptyExpression"] but instead got undefined

The error appears as soon as I update react and react-dom to 17.0.0 and might be related to the new JSX transform in React v17.

Expected behavior

It renders the component as expected without any errors.

System information

OS: macOS Catalina
Version of React: 17.0.0
Version of Next.js: 9.5.5
Version of Node.js: 12.18.3
Version of TypeScript: 4.0.3

Additional context

Add any other context about the problem here.

Issue Analytics

State:
Created 3 years ago
Reactions:5
Comments:17 (7 by maintainers)

Top GitHub Comments

2reactions

messagecommented, Oct 22, 2020

Uhm, rm -rf yarn.lock yarn-error.log node_modules/ build/ .next/ && yarn install && yarn dev fixed my issue 🤔 @jakeherp

0reactions

balazsorban44commented, Jan 29, 2022

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.