Attempted import error: 'isRSC' is not exported from 'react' (imported as 'React').

I’m stuck with this error whenever I try to build I have Tried everything but can’t get rid of it

What I did was just create a new project and then using the C L I npx create-plasmic-app@latest and then need some changes in the project and did plasmic sync Everything works fine when I run it with yarn start But whenever I try to build I get Attempted import error: ‘isRSC’ is not exported from ‘react’ (imported as ‘React’).

Hello @f_f, welcome to the community!

Could you try adding `skipLibCheck: true’ to your tsconfig.json?

Actually I had selected only react without typescript. So what should I turn off? What’s the equivalent if I don’t have ts

Sorry, I thought that was a TypeScript error. Can you paste the full output of the command?

yarn build
yarn run v1.22.22
$ react-scripts build
Creating an optimized production build…
Failed to compile.

Attempted import error: ‘isRSC’ is not exported from ‘react’ (imported as ‘React’).

error Command failed with exit code 1.

Also here is my package.json file

{
“name”: “app3”,
“version”: “0.1.0”,
“private”: true,
“homepage”: “./”,
“dependencies”: {
@ant-design/icons”: “^5.4.0”,
@ant-design/pro-components”: “^2.7.18”,
@plasmicapp/cli”: “^0.1.331”,
@plasmicapp/react-web”: “^0.2.350”,
@plasmicpkgs/antd5”: “^0.0.249”,
@plasmicpkgs/plasmic-basic-components”: “^0.0.228”,
@plasmicpkgs/plasmic-rich-components”: “^1.0.196”,
@testing-library/jest-dom”: “^5.17.0”,
@testing-library/react”: “^13.4.0”,
@testing-library/user-event”: “^13.5.0”,
“react”: “^18.3.1”,
“react-dom”: “^18.3.1”,
“react-scripts”: “5.0.1”,
“web-vitals”: “^2.1.4”
},
“scripts”: {
“start”: “react-scripts start”,
“build”: “react-scripts build”,
“test”: “react-scripts test”,
“eject”: “react-scripts eject”
},
“eslintConfig”: {
“extends”: [
“react-app”,
“react-app/jest”
]
},
“browserslist”: {
“production”: [
“>0.2%”,
“not dead”,
“not op_mini all”
],
“development”: [
“last 1 chrome version”,
“last 1 firefox version”,
“last 1 safari version”
]
}
}

OK I am able to reproduce this issue.

In the mean time, do you mind trying Plasmic with Next.js instead? It has the best support with Plasmic.

No I guess I’ll just have to wait for the fix I don’t have any experience with next.js and also it isn’t really right now what I would need

good that you can reproduce the issue though I think it might be some dependency related issue

hey is there any development on the issue did you find any temporary fix if so please let me know that would be really helpful