If you want to get a quick feel for local development, run
npx create-stackbit-app@latest in your terminal, and follow the instructions.
Stackbit supports developing your project's code locally, including the ability to view your running local site inside Stackbit's user interface with full visual editing.
This is a powerful way to iterate quickly when developing your site - especially when you're making changes to content models or annotations and want to immediately test these changes in the visual editing environment.
Note that viewing your local site within the Stackbit webapp is optional. You can develop locally with just Next.js, without having to run our tooling for visual editing.
We also provide a built-in code editor within our user interface. What's the difference?
- The online code editor is useful when you don't have access to a local development environment, or need to make small tweaks without the hassle to set that environment up.
- The online code editor commits all changes to the project's preview branch immediately. Thus, it's less suitable for changing code while other content editors or developers are also working on the project.
- With local development you have full control over which branch you're working on. Nothing gets committed automatically, and you decide whether and when to commit any changes. You can use your preferred development lifecycle and branching strategy.
- With local development, you have full visibility over the local filesystem and the running SSG process. If something breaks, you can easily restart, cleanup temporary files, and so on.
- Pages show up faster and edits finish quicker, as you're working mostly with localhost with minimal network latency.
- Operating system: MacOS, Windows or Linux (the same as Next.js supports).
- Node version: v14 or later (which comes packaged with npm v6 or later).
- Browser: Google Chrome is currently required. Support for other browsers is planned.
Tip: You may want to use a tool like nvm to run your local site with the best matching Node and NPM versions, while not affecting other installed versions.
Once the project's repository was transferred to you, the Project Settings dialog will show you the commands to clone & run the project locally.
The commands shown in the dialog are similar to the below, with the repository URL already filled and for the
preview branch - but you can create or pick any other branch to fit your needs.
git clone email@example.com:<user>/<repository-name> cd <repository-name> git checkout <branch> nvm use # Optional - only if you're using nvm! npm install npm run dev
You can already make changes to code & content files, and Next.js will refresh the page automatically. Now, let's leave this process running and get your local site displayed within the Stackbit webapp.
Install the Stackbit CLI from the terminal:
npm install -g @stackbit/cli.
The above command specifies the
-g flag to install the package globally and have its executable available everywhere. This may require installing with
sudo, depending on your setup (not needed when using
Run from your local repository's directory:
stackbit dev -d <path-to-dir> from anywhere).
You should see the following output:
% stackbit dev info: Site directory: <path...> info: Found stackbit.yaml, loading config... info: Server started. Forwarding requests to: localhost:3000 info: Open https://app.stackbit.com/local/<token...> in your browser
Click the link shown in the output - this will redirect you straight to the Stackbit editor showing your local site. You can bookmark this URL if you want.
You can now highlight elements, make content changes that will get reflected in your local files, or make code changes locally and see them reflected immediately. That's all there is to it!
Make sure to read things to know.
If something's wrong, jump to troubleshooting below.
By default, Stackbit projects are backed by a remote container managed by us, which is running Next.js over the project's preview branch. What you're seeing in the webapp is that container's output, loaded through an
iframe and proxied by our servers to provide the highlighting and editing experience. Everyone working on the same project work with that container.
In local development mode, the webapp loads the iframe directly from your local proxy (the
stackbit dev process). This proxy serves what your local SSG is rendering, but adds a layer on top to support visual highlights, authenticated content changes, and more.
The URL of the page (e.g.
https://app.stackbit.com/studio/7620acff1hs75ak19ad) is unique to you and is hard-wired to communicate with the
stackbit dev process running on your local machine. It will only work correctly when opened on your machine.
There is no association between local development mode and the regular Stackbit project you've created through the UI. You can use local development to edit
Content editors and other collaborators should keep working with the regular project accessible from the dashboard, as usual.
Regular Stackbit projects always reflect the code in the project's preview branch. When you push code to that branch by whatever means, the webapp will update automatically and changes will be visible to anyone currently working on the project. So make sure to test beforehand, eh?
If you have multiple projects in Stackbit, you can use local development to work with any of them. To switch between code repositories, stop the
stackbit dev process and re-run it from the relevant directory. Note: the shown URL does not change per repository.
Also note the following differences:
- When the webapp is in local development mode, the buttons to share & publish are disabled, as these actions are not applicable.
- The online code editor is not available, as the webapp is agnostic in this mode to what repository your'e running on locally.
- Logs are not shown in the webapp. Check the logs locally (both the web server and
stackbit devemit logs to the terminal).
- As mentioned above, you decide whether and when to commit and push, and which code repository and branch to work with.
Tip: during development, it's natural to make mistakes when defining models or manually editing content files, which can result in rendering errors and stuff generally not working. It's recommended to regularly run
stackbit validate when making such changes to get a verbose check-up of content & models in your code.
When working with cookies in your application, they are often set for the domain and port on which your development server is running (e.g. localhost:3000).
Because Stackbit Dev proxies your dev server through local port
8090, your cookies need to run on localhost:8090. You can achieve this by setting the following cookie:
If the webapp keeps showing "Connecting to local dev environment" with a loading animation:
This message means that the webapp cannot connect to the local
stackbit dev process. Here's what to do:
- Make sure
stackbit devis working on your local machine and its log shows no errors.
- Make sure you're using Google Chrome as your browser, on that same machine.
- If you use multiple user accounts on Stackbit (this is normally not required, as the same user can be a member of multiple organizations): re-run
stackbit devafter logging-in to the desired user, and click the shown URL to open the webapp.
When the connection to
stackbit dev is re-established, the webapp should refresh automatically. If nothing of the above works, re-run
stackbit dev --log-level debug and share the output with us.
If you're seeing "Failed to connect to your site’s local server":
This means that
stackbit dev is working, but cannot access your Next's local dev server (launched with
npm run dev). This usually happens only when Next.js is down or unresponsive.
- Make sure that Next.js is running in its default port (3000).
- Look for errors in the Next.js terminal output.
- Try to restart Next.js. Hot module reloading in dev mode can sometimes get the server unstable.