 – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Deployment error due to missing Sanity package resolved  

Hi everyone! I am the owner of our sanity project but admittedly not a developer. I'm getting some deployment errors that I think require a more capable person than me. Is there a good resource that I could tap into here? Or if I could be pointed in the direction of a solution? Thank you in advance


npm error code E404
npm error 404 Not Found - GET <https://registry.npmjs.org/@sanity/core/-/core-2.36.2.tgz> - Not found
npm error 404
npm error 404  '@sanity/core@https://registry.npmjs.org/@sanity/core/-/core-2.36.2.tgz' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /vercel/.npm/_logs/2025-02-03T17_05_16_751Z-debug-0.log
npm error code 1
npm error path /vercel/path0
npm error command failed
npm error command sh -c cd studio &amp;&amp; npm install
npm error A complete log of this run can be found in: /vercel/.npm/_logs/2025-02-03T17_05_07_857Z-debug-0.log
Error: Command "npm install" exited with 1

wave

This issue was reported in another thread here in the last couple of days.  Sanity seems to have unpublished a package which many sites have as a dependency which are messing with deployments.

I found the thread.  It was accidental and should be restored as of Monday afternoon 

.  You can probably just 'try again' and get it going.



Deployment error due to missing Sanity package resolved

Sanity – Build the way you think, not the way your CMS thinks

Was this answer helpful?