-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Can't resolve '../../public/static/d/...' on build box, but works locally #25605
Comments
I'm seeing this too
|
Is either of you able to share your site so we could drill into the issue?
This should be stable, as this is "hash" generated from your static query text input. It might be related to fact that your local env is on Windows and Netlify is on linux, which could result in subtly different line endings (LF vs CRLF) depending on some git settings - but this is just shot in the dark and even if the hashes are different, it should still build on Netlify |
It seems like my issue was related to #24673 where I was defining |
@BottlecapDave I appear to be experiencing the same issue:
Did you correct the issue? You mention where I was defining gatsby-plugin-typescript. Could you provide details regarding your fix? |
My issue seemed to be around my upgrade process where I had gatsby-plugin-typescript defined in my package.json and also in my Gatsby config. According to the comment I linked, this was no longer needed and seemed to be causing issues, so I removed it from package.json and gatsby config. I assume an older explicit version was being used instead of a newer internal one. Why this only occured on Linux I don't know. It looks like you might be having a different issue, which might be caused by the casing of your contextprovider file (eg contextProvider Vs ContextProvider) which has tripped me up on different os (Linux cares about casing, windows doesn't) |
@chrisworman-pela Could you confirm that this was related to case sensitivity as @BottlecapDave described? |
@freiksenet Yes, I can confirm that my issue was caused by case sensitivity in CI but not local. |
It sounds like this issue is fixed, yes? I'm closing this, but if it's not fixed then please either re-open, or open a new issue. |
Description
After updating my project to the latest gatsby, my builds are failing on Netlify but successful locally. I've seen a few issues that showcases similar results, but their solutions don't seem to be working.
I've updated my build stage to do
gatsby clean
beforegatsby build
and also run the deployment asclear cache and deploy site
.Interesting the names for the static json files are different to what's generated locally, but I'm not sure if this is expected.
Steps to reproduce
N/A
Expected result
The build should be successful.
Actual result
The build fails with the following reports
Environment
Local
Netlfy
The text was updated successfully, but these errors were encountered: