Hi Rincewindwiz,

This looks more like a dependency tree / lockfile problem than a Vercel platform problem, especially because the stack goes through @craco/craco, react-scripts, schema-utils, terser-webpack-plugin, and ajv-keywords.

I'd try to reproduce it from a clean install inside the same folder Vercel is building:

1
cd frontend
2
rm -rf node_modules
3
npm ci
4
npm run build
5

If npm ci fails, your package.json and package-lock.json are probably out of sync. In that case run this locally, commit the updated lockfile, then redeploy:

1
cd frontend
2
npm install
3
npm run build
4
git add package-lock.json package.json
5
git commit -m "Fix frontend dependency lockfile"
6

I'd also avoid npm install --legacy-peer-deps --force as the long-term install command if possible. It can get the build past peer dependency warnings but may also produce a dependency tree that is different from what CRACO/react-scripts expects. If the project genuinely needs legacy-peer-deps, I'd put this in frontend/.npmrc and commit it:

1
legacy-peer-deps=true
2

Then use a normal install command or let Vercel auto-detect it.

For this specific stack, this command should show whether ajv / ajv-keywords versions are mismatched or missing:

1
cd frontend
2
npm ls @craco/craco react-scripts ajv ajv-keywords schema-utils terser-webpack-plugin
3

If the first real error line says something like Cannot find module 'ajv/dist/compile/codegen', then I'd focus on fixing the ajv / ajv-keywords dependency versions rather than changing Vercel settings. The useful thing to share here would be the first 10--20 lines above the require stack, because that usually contains the actual missing module name.

Thank you for this.

Sadly I am the sort of newbie at whom codeless webs/apps is directed and the technical stuff below is way over my head and so I’ll have to give this up and start again with someone other than emergent.

I suspect it may just be an emergent device to persuade people to compile/host on their platform but fighting my way through the techno stuff is just not for me

Thanks anyway

RW

Hi RW,

Totally fair — that kind of npm/CRACO error is a rough place to start, especially if the goal was “no-code”.

Before you abandon the project completely, there may be one lower-tech option: ask Emergent to export or regenerate the app with a simpler modern frontend setup instead of CRACO / Create React App. For example, something like:

1
Please remove the CRACO/Create React App setup and convert this frontend to a standard Vite React app that can deploy on Vercel. Keep the UI and app behavior the same. Make sure `npm install` and `npm run build` work from the `frontend` directory without using `--force` or `--legacy-peer-deps`.
2

The key thing is not really “Vercel vs Emergent” here — it’s that the generated project has an older/dependency-sensitive build setup, and Vercel is exposing that during a clean production build.

If you do decide to try once more, the simplest success check is: does npm run build work inside the frontend folder before deploying? If not, the project still needs to be fixed or regenerated by the tool that created it.