Plasmic app failing to initialize when publishing to Github

Hello, team! I am having trouble publishing to GitHub. The build is failing when “Initializing Plasmic app…” I noticed there was a recent update. Not sure if this is related. I have published application successfully in the past, just not since the update.
The error I am encountering suggests that the Plasmic action is failing because of a dependency conflict between React, Next.js, and the Plasmic Loader package. How do I address and fix this?

Here is my app url.
Project Id - ahPJ61cCdZ3tgEL3s7dn2s

Hello @another_brother,

Can you try it again? It should be fixed now.

@icaro_guerra I am still experiencing the issue. Please advise.


This issue should also be fixed now, sorry for that.

Thanks. We will try again and let you know. Thanks again!

getting the same issue trying to publish as a React app on GitHub; any help please?

==================================================
INSTALLING THE PLASMIC DEPENDENCY
==================================================
npm install --ignore-scripts @plasmicapp/cli
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-scripts@5.0.1
npm error Found: typescript@5.7.3
npm error node_modules/typescript
npm error   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm error   node_modules/fork-ts-checker-webpack-plugin
npm error     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm error     node_modules/react-dev-utils
npm error       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm error       node_modules/react-scripts
npm error         react-scripts@"5.0.1" from the root project
npm error   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.21.0
npm error   node_modules/tsutils
npm error     tsutils@"^3.21.0" from @typescript-eslint/eslint-plugin@5.62.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm error       node_modules/eslint-config-react-app
npm error         eslint-config-react-app@"^7.0.1" from react-scripts@5.0.1
npm error         node_modules/react-scripts
npm error       1 more (eslint-plugin-jest)
npm error     tsutils@"^3.21.0" from @typescript-eslint/type-utils@5.62.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"5.62.0" from @typescript-eslint/eslint-plugin@5.62.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm error         node_modules/eslint-config-react-app
npm error         1 more (eslint-plugin-jest)
npm error     1 more (@typescript-eslint/typescript-estree)
npm error   1 more (the root project)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm error node_modules/react-scripts
npm error   react-scripts@"5.0.1" from the root project
npm error
npm error Conflicting peer dependency: typescript@4.9.5
npm error node_modules/typescript
npm error   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm error   node_modules/react-scripts
npm error     react-scripts@"5.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2025-02-04T19_02_58_836Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-02-04T19_02_58_836Z-debug-0.log

Hello @lyrold_careto, it seems that the latest updates to react has broken create-react-app, which we use to set up the codegen version for react.
We recommend using the nextjs for now while we work on changing the use of create-react-app.

1 Like