[Bug]: Assets not loaded when running frontend alongside DCR locally

[SiAdcock]

The dev workflow of running DCR alongside frontend is currently broken. We are attempting to load JavaScript assets from the wrong place, so JavaScript doesn't get loaded in this scenario.

You can run both frontend and DCR then hit the frontend port on localhost:

http://localhost:3000

DCR's rendered output generates a relative path with a leading slash that roots the path:

<script type="module" src="/assets/frameworks.client.web.js"></script>
<script type="module" src="/assets/index.client.web.js"></script>

Because you're hitting frontend at localhost:3000, the browser attempts to load asset scripts from:

http://localhost:3000/assets/index.client.web.js

Instead of:

http://localhost:3030/assets/index.client.web.js

First reported here.

@chrislomaxjones suggests taking inspiration from #5285 and #3471

It's possible this is a bug in frontend rather than DCR. If this is the case, we should probably write a check in frontend that loads paths beginning with /assets from localhost:3030 instead of localhost:3000.

[alinaboghiu]

I think I'm getting this issue regardless of which url I use for DCR?
I managed to get it working by making sure that we use the hashed asset map when running locally (by setting this fallback value to true): https://github.com/guardian/frontend/blob/main/common/app/common/configuration.scala#L415

[emdash-ie]

I have also run into this problem locally when running frontend and DCR, with frontend pointing at CODE capi. Unfortunately tweaking that config value hasn’t worked for me (assuming the link above is slightly old and it’s supposed to point to assets.useHashedBundles?).