Join the Webstudio community

Updated 4 months ago

Cannot export project created in local builder

At a glance

The community member is using the Webstudio builder setup on their local machine to create dynamic pages, but is unable to export the project using the Webstudio CLI method. The community members discuss that the CLI is generally working for publishing in the Webstudio cloud, but the local project is not working as expected. They suggest using wstd.dev instead of localhost when opening the builder, as wstd.dev points to the local machine and provides SSL termination. However, the community member is still experiencing issues with fonts and images not downloading properly when using the share link from the local project. They try various steps like deleting the previous folder, re-uploading the images, and recreating the folder, but the issue persists. Finally, a community member suggests passing the --preview flag to the webstudio build command to resolve the issue.

Useful resources
Hi, I am using the webstudio builder setup in my local machine, to create dynamic pages.
I am not able to export the project using Webstudio CLI method.

How can we deploy a project built locally ?
4
O
S
J
66 comments
hey, this is not giving us enough information to help you
generally its working, because the same cli is used to publish in the webstudio cloud
Please see the screen record. This is what I am trying to do. The same steps I did using the share link from cloud project it worked for me. It is not working for me when I am using a share link from the local project.
when you open builder use wstd.dev
don't use localhost
where did you get the localhost? we need to update the docs or wheever you found that
wstd.dev will point to your localhost
but you need to use wstd.dev for ssl termination
The VS code prompts to open in browser and it opens using localhost.
whats the version of your CLI?
sorry, actually what's printing it is pnpm dev command not the cli
when did you pull the builder?
this is what it should look like when you run pnpm dev:

Plain Text
> @webstudio-is/[email protected] dev /workspaces/webstudio/apps/builder
> remix vite:dev

  ➜  Network: https://wstd.dev:5173/
  ➜  press h + enter to show help
`
vscode just looks for the port on that dialog. I talked to ivan about this a while ago and he found a way to remove the dialog from coming up but I guess we didn't decide forsure if that's what we should do
Attachment
image.png
Thanks @Oleg Isonen @John Siciliano for the responses.
It is pretty recent. Some day last week. And it is showing the https://wstd.dev:5173/
But thought it will work with localhost also. And it was not mentioned anywhere in the document not to use localhost.
Sure, Got it πŸ‘
If you see localhost recommended anywhere please let us know
Yes, not noticing was my bad!
@Sony Antony Can you take a screnshot of that dialog so i can make note of it in docs? My screenshot has the tooltip so I dont want to use it
You are Welcome!
Now, I am using https://wstd.dev:5173/ to open the builder and I have a share link creted. But My fonts and images are not dowloaded properly. It shows error.
Attachment
image.png
did you delete the previous folder?
it had probably localhost url
actually the errors say url is ok
try opening one of those urls, is image there?
is image in the builder in asset manager?
might have to do with how you initially uploaded those
I can't find the images in that URL
I removed all images
re-uploaded a few images
Ye, all images are in there
And still getting the error as below
Attachment
image.png
My page looks like this.
Do you think cache has something to do with this? There are both "no-images" and "broken images" in the rendered page.
Attachment
image.png
try opening one image from the error in the browser
just in case recreate the folder and generate a new share link
I have a suspicion running it with localhost has caused multiple broken things
I tried this already. But I will start anew and see if it helps.
Need to pass --preview flag to webstudio nuild command
@Sony Antony @TrySound Do you have clear steps for exporting the project created in local builder?
I'm currently experiencing the same issue.
Hi, Are you trying to export from from local setup or from cloud dashboard?
Hi @Sony Antony. Have you been able to export static or dynamic projects from the local builder?
On my end when export it says
Not implemented, use buildId=d279d7b1-7379-4b02-b138-49cf67e12bdb error.
This is expected error. After getting it you need to do the rest manually with webstudio cli.
Installed the CLI and can export the project now. Huge thanks @TrySound !

I initially thought I could just export via the CLI, and all recent changes would automatically be included. Turns out you still need to hit the Publish button (even if it shows an error) before using the CLI to make sure the latest changes are exported.
Yes, this is some kind of versioning under the hood
Allows us to restore published site if deployment got broken somehow
Any ways to auto-save or backup the changes made with the builder or run publish command automatically? If needs to be done manually only, a keyboard shortcut for the Publish action could work
We will expose publish hook and let users build own workflows for both local and cloud
For now only publish and then cli will work
That'd be so freaking powerful! Thanks bringing that up!
Btw, any advice on how to export the images to the /assets folder? When exporting my project this is the error I'm getting on the images.
Error in downloading file Meeting_02_best_wvChsxAQTHaK50a7y4B9m.webp Error: Failed to fetch
You need to use --preview flag
It is specific to dev environment
@TrySound ... thx for this direction ... everything works perfectly. a) hit publish b) webstudio --preview c) npm run dev
@TrySound one question ... why does this significant delay happen even on the self-hosted builder version for "publishing process in progress" even though it is not implemented ... can that delay be removed?
Figured out @TrySound ... I cut all timeouts in domain.tsx and publish.tsx by 1000 and its super now!
Add a reply
Sign up and join the conversation on Discord