-
Notifications
You must be signed in to change notification settings - Fork 189
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
Build files not found net::ERR_ABORTED 404 #285
Comments
Not resolved but might as well close. |
Hi Chris, Did you find a solution? |
I didn't. I wasn't able to use GH pages and instead made a server and used Heroku for that project. |
True. I kept trying and tweaking things here and there... and at some point it worked. Not sure what did it, really. I think GitHub struggles to clear previous versions of the site, so that makes debugging more difficult. Thanks, though |
hi there,, anyone find a solution? best |
@meta-meta FYI Medium link is paywalled |
You need to set the "homepage" key in package.json. For example: “homepage” : “https://yourgithubname.github.io/yourreponame", |
I've the same problem .. any one find a solution ? |
|
hey I was having the same trouble using vue but found this while googling so I'll share this in case anybody else does. so I just changed it like this and now everything works, probably my fault because of something that I did at some point but hope that helps |
For me, the problem was that it wasn't properly navigating the folder structure.
working version:
Add a "." before the "/assets/...." part and the error will go away I had to manually do this. I don't know how to get react to build it correctly |
That worked for me! Thanks a lot! It seems that when the |
Hello guys. ("vue-invoices" is the name of my project) Styles are displayed on this path: Path in index.html in the dist folder after the npm run build command I think the issue is not that we're writing something wrong, but that GitHub for some reason doesn't want to display what we give it. I decided to check something and purposely wrote a non-existent path. So here are my paths after I created the project with the npm run build command: <script type="module" crossorigin src="/vue-invoices/assets/index-1037ce7e.js"></script> In styles, I purposely change the path to href="/vue-invoices/non-exist-folder/index-b3d70005.css"I write a commit, wait 2 minutes, and go to the project site to see what's written in the head tag. --> My updates didn't go through. Why? Maybe I got a ban because I updated the paths many times. |
I got email from gitHub pages build and deployment: Some jobs were not successful |
I just discovered the Actions tab. |
So my story comes to an end. Do not repeat my mistake and be careful. |
< base href="./" > |
I had this issue with my React project. My solution was as follows: I realized that I needed to modify the package.json file by adding the 'homepage' key, and the value should be the URL generated for GitHub.
|
This worked perfectly for me. But I have do edit manually the index.html file on gh pages branch. Thank you |
If you use react-router-dom, the root of the application is always |
Hey. I have the same issue and did the same as you mentioned. I added a dot before /assets in the html file in my dist folder. |
I had the same issue as well. I fixed this by switching my main branch to gh-pages on github and then directly, on github, modified my index.html file to be the correct file path. My project was already deployed then and it properly updated the page after a few minutes. |
Probably this is common. I get 404 to all my build files.
Gh-pages will not find my files from
create-react-app
inside the build folder. I've tried moving them out, which has worked before. I manually renamed them this time but still not being found.Actual place:
https://github.com/chrisdel101/baseballhack/blob/gh-pages/static/css/main.56da8e78.chunk.css
Where gh-page is looking:
https://chrisdel101.github.io/static/css/main.56da8e78.chunk.css
Spent a few hours on this now including following all the orthodox steps in CRA deployment tutorials.
The text was updated successfully, but these errors were encountered: