-
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
[v2] [unconfirmed] Gatsby doesn't properly delete files on build #7942
Comments
/cc @pieh |
Just checked this on the latest commit of crowdswap/landing - I cloned, ran @dfmarulanda I'm assuming this is a problem with how Azure is caching certain resources, since it's working perfectly for me - closing. Please let me know if you have any further issues, but I think this is an issue with your deployment rather than with Gatsby. |
@dfmarulanda (please make further replies in this issue, rather than #7355) I did some investigating and I think the issue could be caused by Azure not updating all the pages, rather than Gatsby - theoretically it should work if Azure deploys the |
Having said that, I'd still recommend you try to build the site on Azure, rather than your current approach, since it would make the git repo easier to manage. |
This sounds like a bad npm/yarn install problem. The only possible issue with files in |
I deleted everything, indeed it worked perfectly for weeks. I changed my deployment process and now it's working perfectly. I decided to use Azure Blob Storage instead of Azure Web App. Working like a charm. |
I don't know but I just looked into my public folder and was huge of .map and .js.map files. I don't think they get wiped all the time properly. |
@hackhat that's very good point, we should expand globs used in gatsby/packages/gatsby/src/bootstrap/index.js Lines 133 to 148 in 42a2d07
to cover map files |
@dfmarulanda has pointed out that
gatsby build
doesn't work reliably without first deleting thepublic
folder - we should guarantee that runninggatsby build
over an existing build results in a working website.The text was updated successfully, but these errors were encountered: