Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make hash for fetch.js optional #1638

Open
coder-hugo opened this issue Jun 10, 2022 · 0 comments
Open

Make hash for fetch.js optional #1638

coder-hugo opened this issue Jun 10, 2022 · 0 comments

Comments

@coder-hugo
Copy link

Summary

If you do not use the fetch functionality it would be nice if you could prevent gridsome from rendering the hash to each and every page.

Basic example

Motivation

I'm trying to optimize the deployment of our gridsome app. With the default configuration the content of each and every page changes with every build although the page data is identical. To fix this I adapted the webpack configuration of our project to use stable hashes in the asset filenames. But the content of the pages still changes as the hash for the fetch.js is different for every build. This means we have to upload each and every page again although just a few of them really have changed. The output of our project has some hundreds of mega bytes so the deployment takes unnecessary long due to the changing hash in each and every page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant