plenti: Can't remove "%v" folder from previous buildunlinkat ./public: directory not emptypublic
Hi @jimafisk
I just wanted to report this error. Unexpectedly this morning after pushing some changes to Github I got the following error. It only happened the one time and I was able to re-run and serve the site as if nothing had happened. So maybe just something to monitor for now unless you can see what might have caused it.
NOTE: I have upgraded to the latest release v0.6.0. The error happened in the educenter theme
Serving site from your "public" directory.
Visit your site at http://localhost:3000/
Could not compile 'core/cms/fields/radio.svelte' Svelte component: Unable to write compiled client file: open public/spa/core/cms/fields/radio.js: no such file or directory
2023/01/13 08:16:21 build.go:115:
Can't remove "%v" folder from previous buildunlinkat ./public: directory not emptypublic
Regards, Ben
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 20 (10 by maintainers)
Commits related to this issue
- Don't watch hidden dot files (#261). — committed to plentico/plenti by jimafisk a year ago
Hi @jimafisk It is serving fine now. I just closed everything down and reopened and it worked. there might have been a conflct with another Plenti theme project I had open and on the same port
localhost:3000😊So all good thanks.
No, it seems to work fine on my end. Is a
publicbuild folder getting created at all? Are there any html files in it?Hi @jamestagal, Just want to double check that you’re going to http://localhost:3000/apsho/ not http://localhost:3000/ right? I think this site uses a baseurl. Thanks!
Hi @jamestagal,
I believe the
Can't remove "%v" folder from previous builderror was happening if two save events happened in a row (some editors do this automatically). I tried making some improvements to the batching process in the file watcher, so I think this might be fixed in v0.6.13, can you test when you get a chance and let me know if this is working any better on your end?Thanks for flagging this @jamestagal. I’ve seen a couple of weird builds since I’ve changed the internals around. I’m going to be doing some additional restructuring of the build in the near future (https://github.com/plentico/plenti/issues/255) to make improvements there so that might resolve some of these issues. If you can pinpoint what’s causing this, just let me know! Thanks!