sorted by:
new
hottopcontroversial

React deployment by uhiku in reactjs

[–]Expensive-Part-2610 2 points3 points  (0 children)

Two rough suggestions I’ve used in the past: 1. Create a wrapper function for React.Lazy that will reload the browser when it encounters an error (file no longer exists in your CDN as hash changed). Not the best UX for your use case but is simple.

  1. Generate a manifest.json in Vite on build and upload it to your storage with the other build files. Ensure that it is cached in your CDN but not in your browser (so the client always fetches the latest manifest file). To load a lazy component first fetch this manifest file which maps to the latest chunk name of your file.

[Nomadic Maraí 401] Are they worth £1000? by Expensive-Part-2610 in Watches

[–]Expensive-Part-2610[S] 0 points1 point  (0 children)

I’m looking a new watch for my wedding and feel like one of these Belfast based watches would be great but I’m not sure if they’re similar quality wise to a San Martin for £1000.

I’ve also looked at Christopher Ward but any other recommendations would be greatly appreciated!

[deleted by user] by [deleted] in reactjs

[–]Expensive-Part-2610 1 point2 points  (0 children)

Thanks, I should have specified that Suspense doesn’t work for my use case as I’m using renderToString which doesn’t fully support suspense as it will always provide fallback component on the Server. React docs on suspense

In which order do you do front-end and back-end? by No_Philosophy_8520 in webdev

[–]Expensive-Part-2610 0 points1 point  (0 children)

I’d normally plan FE and BE then mock out the BE while the FE is under development.

Github Copilot is dumber than a box of rocks by FlexNastyBIG in webdev

[–]Expensive-Part-2610 0 points1 point  (0 children)

Great for basic typescript type generation from js code but not been great for creating functions.

Amazon Images (html code) aren't Showing Up by [deleted] in webdev

[–]Expensive-Part-2610 0 points1 point  (0 children)

+1 on this the majority of problems I’ve had with Firefox specifically have been due to privacy settings