Stuck on the Getting started instructions.

What are we supposed to use for the Project output path, when running sanity init --env?

If you just leave the default path it just creates a brand new Sanity project, so you have a new Sanity project within each the App and Studio folders. That doesn't make sense to me. Meanwhile, you can't select a folder that already has files in it.

Isn't the Studio folder supposed to be where the sanity project is? Ie. not a subfolder of Studio or App.

Hello!

I just went to install this and followed the readme and ran into a couple of minor errors when getting the project setup and running. Happy to make a PR for this if it helps. The second issue is maybe a bit more nuanced, IIRC there is a reason within SvelteKit to preface env variables with PUBLIC? I might be forgetting something there but I wonder if there is a need for that prefix.

1. The command npm create sanity@latest init --env doesn't seem to work correctly, however sanity init --env does. The npm create command runs through a full install of Sanity without outputting an env variable. I think the correct command should be npx -y sanity@latest init --env.
2. In the SvelteKit app the environment variables it is looking for are PUBLIC_SANITY_DATASET and PUBLIC_SANITY_PROJECT_ID. When you run the sanity init --env command it spits out SANITY_PROJECT_ID and SANITY_DATASET with our the PUBLIC prefix. The easiest fix for me was to just correct the environment variables themselves.

The package.json file informs us that .js files are interpreted as native JavaScript modules with import and export keywords.

This causes an error when deploying the current build.

Suggested Fix: Rename postcss.config.js to postcss.config.cjs

Reference

Is your feature request related to a problem? Please describe.
I couldn't see that this provides visual editing, which seem like a mess to add. Hope I'm wrong. https://www.sanity.io/docs/visual-editing

Describe the solution you'd like
Sanity studio visual editing.

Describe alternatives you've considered
This is the new way for live preview while editing in Sanity studi as far as I can see.

In the Getting started section on step 2 it says that you can use the 'sanity init --env' if you have the CLI installed.

This didn't work for me. When I tried the CLI it said that it was for V2

but then asked if I wanted to continue with the V3 installation.

I said yes and it just went ahead and created a whole new studio directory rather than just the .env file in the way that the npm package does.

Suggested Fix: Remove the line about using the CLI.

I followed the readme to bring up a working example on my local machine. I created content in the studio and was able to see it in the list of posts. However, when I clicked on it I got a 500 error. Based on the readme I would expect to be able to view the content.

I did find a work around by adding http://localhost:5173 to the list of CORS origins in the sanity portal by following the doumentation at https://www.sanity.io/docs/cors.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Using a curated preset maintained by

Sanity: The Composable Content Cloud

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• chore(deps): lock file maintenance

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency vite to v4.5.2 [security]
• chore(deps): update non-major (@babel/core, @babel/plugin-syntax-jsx, @babel/preset-typescript, @portabletext/svelte, @portabletext/types, @sanity/client, @sanity/types, @sanity/vision, @sveltejs/adapter-auto, @sveltejs/kit, @types/react, @types/styled-components, autoprefixer, eslint, eslint-config-prettier, fast-glob, fs-extra, groq, postcss, sanity, svelte-check, typescript)
• chore(deps): update dependency @sveltejs/adapter-auto to v3
• chore(deps): update dependency @sveltejs/kit to v2
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency prettier-plugin-svelte to v3
• chore(deps): update dependency svelte to v4
• chore(deps): update linters to v6 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• fix(deps): Update dependency styled-components to v6
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository