This is my first Sage 10 build. Site was ready to move to staging env, so I thought I’d run composer update beforehand, and got the errors that led to me updating Acorn to v3.0.
I updated Acorn as per the docs (thanks!), ran yarn build, and everything went smoothly moving to staging (via SFTP), and later to production.
Back working on the dev site and yarn dev works as before, except when I change a blade file, or even just refresh the page, I get errors on localhost:3000 that I wasn’t getting before - but only when DevTools is open. If I close DevTools localhost:3000 runs and updates as normal, until I reopen DevTools again.
The breakpoint in DevTools is flagging in app.css on line 39:
var ___CSS_LOADER_URL_REPLACEMENT_15___ = ___CSS_LOADER_GET_URL_IMPORT___(___CSS_LOADER_URL_IMPORT_15___);
I can’t see what the error is and all the fonts seem to be loading correctly, just as they do on staging and production. Has anyone had this type of error before? Is it due to updating Acorn? I can see another update has come out to v3.1 but I haven’t done that yet.
What version of Bud are you on? If you aren’t on at least v6.6.8 then I’d recommend upgrading
What does your Bud config look like?
so I thought I’d run composer update beforehand, and got the errors that led to me updating Acorn to v3.0.
Just running a composer update without being specific about what packages you’re wanting to upgrade will likely result in errors in general — that’s a dangerous command to run on a codebase IMO. Look into tools like Renovate and Dependabot for upgrading individual dependencies, one at a time (unless they’re related of course).