You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on an earlier comment #191 (comment). We should auto-generate a hash that could be used to store the clientside app. Each time a new build is made the folder name will change and invalidate the previously cached app. This will fix issues where the correct HTML loads initially, but then the app hydrates and it shows the previously cached version (as seen here). In the future it would be great to only bust the cache for the specific files that changes, but for now this might be the quickest / easiest approach.
The text was updated successfully, but these errors were encountered:
Important: This API is subject to change (might end up using different variable names).
You can set this in plenti.json like:
{
"entrypoint_js": ":fingerprint"
}
Note that if you omit the entrypoint_js key, it defaults to spa for backwards compatibility.
Also, we also renamed the former entrypoint key to entrypoint_html to avoid conflicts - currently this isn't being used because using a dynamic svelte component in router.svelte was throwing console errors.
If using :fingerpring, the value is dynamic so you'll want to set it using magic prop env.entrypointJS in your <head> like:
Following up on an earlier comment #191 (comment). We should auto-generate a hash that could be used to store the clientside app. Each time a new build is made the folder name will change and invalidate the previously cached app. This will fix issues where the correct HTML loads initially, but then the app hydrates and it shows the previously cached version (as seen here). In the future it would be great to only bust the cache for the specific files that changes, but for now this might be the quickest / easiest approach.
The text was updated successfully, but these errors were encountered: