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
This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
Note that if you remove the import directive from gatsby-browser.js and run the same script, the build diff is now empty. Which proves that the culprit is the import directive.
Preliminary Checks
Description
When importing a CSS file from gatsby-browser.js as described in https://www.gatsbyjs.com/docs/how-to/styling/built-in-css/, all files are generated with each build, even if no changes.
Therefore, it seems the import CSS directive is breaking the incremental build.
Similar issue reported: https://www.reddit.com/r/gatsbyjs/comments/z37o2o/is_the_webpackcompilationhash_supposed_to_change/
Reproduction Link
https://github.com/thierrygoldwaser/gatsby-incremental-build-ko
Steps to Reproduce
(As described in https://www.gatsbyjs.com/docs/debugging-incremental-builds/, the compute-build-diff.sh script computes a diff between 2 consecutive builds.)
Expected Result
File build-diff.diff should be empty.
Actual Result
File build-diff.diff is not empty.
Note that if you remove the import directive from gatsby-browser.js and run the same script, the build diff is now empty. Which proves that the culprit is the import directive.
Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: