I have installed Pega 8.7 personal on my local windows machine as well as downloaded the Pega React starter pack from the pega marketplace.
But I am facing problem while launching the react app. The details are mentioned in the attached document.
The system is not able to identify “react-scripts”.
Can you please let me know I am missing here.
PegaReactStarterKit_Issue.docx (125 KB)
Can you confirm that you installed VERSION SP-R.87.1 from latest MarketPlace link and meet the required development environment?
Can you confirm that you set your package.json file to reference the following: “react-scripts”: “4.0.3”?
Can you provide the full install output? From the output we should see something like > npm WARN audit Updating react-scripts to 5.0.0If this is being set to a later version ). The 5.0.0 version does not yet work with React Starter Pack…mostly due to the semantic-ui dependencies. We will be upgrading to this version of react-scripts in a future release. For now you should set your package.json file to reference the following: “react-scripts”: “4.0.3”,
As per ReactApplication.pdf file:
(" DO NOT use npm audit fix --force to try to fix vulnerabilities enumerated
during a npm install. This has been known to frequently make a breaking change by lowering the
version ofreact-scripts within package.json.")
Did you already see the below posts to help you with the install?
How to install React JS and how to use react components in pega 8.2
@SomitC37 issue resolved by deleting package-lock.json and updating npm dependencies
@MarijeSchillern & @SomitC37 : For SP-R.87.1 within package.json the reference should be:
“react-scripts”: “5.0.0”,
We did upgrade to 5.0.0 react-scripts with this release of React Starter Pack and that version of react-scripts should be utilized.
@SomitC37 Happy to hear issue is resolved. In general you should do an npm install as part of setup for a newly retrieved starter pack. I looked at the package-lock.json file included with SP-R.87.1 and see it properly referencing react-scripts 5.0.0 (so key step was likely just running npm install)
