Parsing error in `schemas` folder, potential linter issue

Wondering if anyone else has run into this — I have an error popping up only in my

schemas

folder for some reason:
Not entirely sure what’s causing it, I’ve tried googling the error and making suggested changes to my various config files but so far nothing I’ve tried helps. I’m not super familiar with what’s going on behind the scenes with some of these node packages that come with Sanity so any guidance would be appreciated.

For what it’s worth, I moved this

studio

directory from a different directory, and everything seems to be working fine at least in development (data and sanity studio are working fine on localhost:3333 and in local front end), but I can’t figure out what’s causing this parsing error.

I can confirm the module is definitely in there

looks like this. maybe I’m missing something?

It doesn't look like anything there is causing it. Do you have a

.babelrc

or

babel.config.json

in your project?

I don’t think so, that wouldn’t go in the

node_modules

right?

No, it would have been something you set up in the root of your Studio. Hmm, I'll keep exploring.

No, it would have been something you set up in the root of your Studio. Hmm, I'll keep exploring.

Was there a resolution to this?I am having the same issue, clean install of Sanity from the cli.

So far I haven't found any — I can check again later today if the issue is still happening but so far it hasn't prevented anything from working. Could be a linter issue?

I’m having this issue too on a clean install from CLI v2.27.0. At this stage, it seems limited to a linter issue. Did anyone find a solution?

If others are still having this issue, my fix was related to the way VS Code deals with opening a project with multiple sub projects
Project
|--- /web

If others are still having this issue, my fix was related to the way VS Code deals with opening a project with multiple sub projects
Project
|--- /web

If others are having this error, my issue was related to the way VS Code deals with a project containing multiple ESLint working directories (common in monorepos).
For example:

Edit`./.vscode/settings.json` to include my ESLint projects
.
Hope that helps :-)