Sage 10 runtime.js issue

This is my first time trying to set up Sage 10. I’ve installed WSL and PHP8, node, nvm, composer and yarn on my ubuntu server.

I had previously set the website up via WAMP (and this is where my DB etc is) but if I visit from localhost - admin all works fine etc - but the frontend I just seem to have an issue with:

file_get_contents(C:\wamp64\www\website/wp-content/themes/sage/runtime.16d785.js): Failed to open stream: No such file or directory

The file however in VS Code does exist, any ideas why this would be?

You’ve got directory separators going both ways in this address, which is wild and potentially part of your problem. I’m not sure where that’s coming from. If you’re using WSL, you shouldn’t be seeing any C:\ file paths–they should all look like /mnt/c/ or something.

So my WP install is via my WAMP. Probably why it’s picking up the windows style path. I’m in the process of installing Apache and mysql server on my WSL but was hoping to not need two envs. Hopefully switching fully to WSL will solve?

Found the info for what Sage 10 needs quite vague in the docs so been looking at some other guides.

I’m having exactly the same issues. Only happens when i run yarn build, NOT on yarn dev.

file_get_contents(C:\wamp64\www\leo_v2/web/app/themes/leo_v2/runtime.16d785.js): failed to open stream: No such file or directory

I too have my site on WAMP.

With the env file of bedrock set to development, the error page shows making the site unusable. I uploaded my site to a web server to test and Query Monitor still reports the file missing there, even with correct address structure.

file_get_contents(/home/myusername/staging.mywebsite.com/web/app/themes/leo_v2/runtime.16d785.js): failed to open stream: No such file or directory

Update: I updated Acorn to v2.0.0-beta.9 and the issue seems to be fixed?

1 Like