I’m having trouble with the npm preparation stage when building Guidewire ClaimCenter from command line. The build process downloads most packages successfully but then crashes with this error:
npm ERR! code E404
npm ERR! 404 Not Found - GET registry.npmjs.org/@npmcli%2fdocs
npm ERR! 404 '@npmcli/docs@^1.0.0' is not in this registry
The weird thing is that everything works fine when I build and run the server through the studio interface. It’s only the command line build that has this problem. The error seems to happen when npm tries to fetch some documentation package that doesn’t exist in the registry. Has anyone else run into this issue with ClaimCenter builds?
yeah, check your npm version, older ones mess things up. also, try running it with --verbose to get more info on the error. hope it helps!
Had the exact same problem last year with ClaimCenter. Turned out to be npm cache corruption - it broke command line builds but studio builds worked fine. Run npm cache clean --force, then delete your node_modules folder and package-lock.json file before building again. My @npmcli/docs package got cached wrong from a failed install. Also check if you’ve got corporate proxy or firewall settings messing with registry access during automated builds.
Switch to a different npm registry temp - the main one sumtimes has issues with specific pkgs. Run npm config set registry https://registry.yarnpkg.com then try ur build. If it don’t work, revert with npm config set registry https://registry.npmjs.org/. Fixed the same 404 errors I had on enterprise builds.
Sounds like a registry timing issue - your command line build hits different npm mirrors than the studio. I’ve seen this exact thing with enterprise builds where manual works but automated fails.
Skip wrestling with npm cache and version conflicts. Just set up automation that handles the whole build pipeline properly. Create a workflow that manages npm install with error handling and fallback registries.
I use Latenode for this build automation - it handles registry inconsistencies really well. Set it to retry failed packages from different mirrors, auto-clean cache when builds fail, and switch between npm configs based on what’s working.
Best part? You can monitor the whole ClaimCenter build and get alerts when stuff breaks instead of finding out during deployment.
Check it out: https://latenode.com
This is a package resolution mismatch between your studio and command line environments. The @npmcli/docs error means your npm registry settings are different in each setup. Studio’s probably using a different .npmrc file or registry than your command line. Check if there’s a project-specific .npmrc in your ClaimCenter directory that studio reads but command line doesn’t. Could also be Node.js version differences - studio might be running a different version that resolves dependencies differently. Run npm config list in both environments and compare the registry settings. You’ll likely need to set the registry URL in your command line to match what studio uses.
Hit this same issue last month during a ClaimCenter deployment. Command line builds don’t inherit studio’s npm config - studio has its own embedded setup that skips certain registry checks. Fixed it by updating the npm dependencies in package.json and removing deprecated @npmcli packages. Check your dependencies and devDependencies sections for outdated tooling packages that Guidewire bundled but aren’t maintained anymore. I manually updated several @npmcli references to newer versions or ditched them completely if they weren’t actually needed. Once I cleaned up package.json, command line builds worked fine.