❗️ Build error with Fluid Sanity Studio (vite alias issue)

[ldifazio]

Hi team,

I've followed the README from scratch using npm create fluid@latest.
When trying to build or start the Studio, I get this Vite error:

`File: /Users/XXXX/Sites/headless-filo/sanity.config.ts:9:33
1 | import { defineSanityConfig } from "~/sanity/config";
| ^
2 | const projectId = process.env.PUBLIC_SANITY_STUDIO_PROJECT_ID;
3 | const dataset = process.env.PUBLIC_SANITY_STUDIO_DATASET;
at TransformPluginContext._formatLog (file:///Users/XXXXXXX/Sites/headless-fio/node_modules/vite/dist/node/chunks/dep-DBxKXgDP.js:42499:41)
at TransformPluginContext.error (file:///Users/XXXXXX/Sites/headless-filo/node_modules/vite/dist/node/chunks/dep-DBxKXgDP.js:42496:16)
at normalizeUrl (file:///Users/XXXXXX/Sites/headless-filo/node_modules/vite/dist/node/chunks/dep .....

I haven’t changed anything from the default install. The alias ~ points to app/, but it seems to break during the Studio build (Sanity v3). Full error trace included below.

Is this a known issue, or should I update something in vite.config.ts or sanity.config.ts?

Thanks in advance 🙏

[thomasKn]

Hi @ldifazio, can you share you node and npm versions (node -v && npm -v)?
Also, what package manager do you use?

[ldifazio]

Hi @thomasKn 👋
Thanks for your reply!
Here’s my environment

node -v && npm -v v20.11.1 10.5.0

Package manager: npm
I used npm create fluid@latest and followed the README exactly.
When I try to run npx sanity dev to start configuring the Studio, I get this error:

[vite]: Rollup failed to resolve import "~/sanity/config" from "sanity.config.ts". Does the file exist?

It seems like the alias ~ (pointing to app/) is not working properly inside the Studio config.
I haven’t changed anything in the default setup.
Do I need to adjust something in vite.config.ts to make the Studio build work?
Thanks again 🙏

[thomasKn]

@ldifazio this project is embedding the Sanity Studio (docs here), which means you don't have to run a dev server (npx sanity dev) for the Studio. You also don't have to build and deploy the studio. The studio lives inside the /cms route.