Issue with @babel/types causing deployment blockage, workaround provided.

17 replies

Last updated: Nov 2, 2021

Is there any fix for this ?

AI Update

I'd be happy to help you troubleshoot an issue with Sanity, but I don't see any error message, code snippet, or description of the problem you're experiencing in your question.

To help you effectively, I'll need more information such as:

What error message are you seeing? (Copy the exact error text if possible)
What were you trying to do? (e.g., setting up a project, querying data, configuring the Studio)
What code are you running? (Share relevant snippets)
What's your environment? (Sanity Studio version, framework, Node.js version, etc.)

Common issues people encounter include:

CORS errors when accessing the API from the browser
Schema validation errors when defining document types
Build errors related to Node.js version compatibility (Studio v4 requires Node.js 20+)
Query errors with GROQ syntax
Deployment issues with Vercel, Netlify, or other platforms
Authentication problems with tokens or project access

Feel free to share more details about what's happening, and I'll be able to point you to the right solution or documentation!

Hi! We’re looking into it!

Glad to hear it! Experiencing the same issue here.

Thank god thanks for the update

user Y

!!It means a lot.

Thank god thanks for the update

user Y

!!It means a lit.

user Y

thanks for having a look

We have indications that it’s related to an upstream dependency. Hopefully we’ll be able to push a fix in not too long

Thanks

user Y

! It does seem to correlate time wise with the introduction of babel 7.16.0

should i try installing babel version 6 ?

Is there any progress? This issue is currently blocking one of our deployments

user L

just posted on the github issue -> “Hi we’re aware of this issue and it’s very high priority for us. We’re actively looking for the root cause but for now you can get around this issue by using yarn `resolutions` or

npm-force-resolutions

.So far we’ve isolated it to

@babel/types

.To force an older version of

@babel/types

, add the following to your

package.json

and then reinstall:

{

  "name": "mysanityproject",

  "keywords": ["sanity"],

  "scripts": {

    // 👇👇👇 (only if you use npm) add this to your scripts

    "preinstall": "npx npm-force-resolutions"

    // 👆👆👆

  },

  "dependencies": {

    "@sanity/base": "^2.21.7",

    "@sanity/components": "^2.14.0",

    "@sanity/core": "^2.21.7"

  },

  // 👇👇👇 Add this regardless if you're using npm or yarn

  "resolutions": {

    "@babel/types": "7.15.x"

  }

  // 👆👆👆

}

• If using

npm

npm-force-resolutions

will run prior to your install and create a

package-lock.json

file that resolves the compatible versions.• If using

yarn

, resolutions are built in and it should work after a

yarn

installAfter the reinstall, the graphql deploy should work.”

fantastic that’s worked, thanks!

user X

lol, sorry! Appreciate the quick fix!

Hi this should be fixed properly in v7.21.8. Feel free to remove those other workarounds. See here

Thanks for the response folks!!

Sanity – 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.

Get started for free Explore the demo

Issue with @babel/types causing deployment blockage, workaround provided.

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

Was this answer helpful?