I have a React App that I'm trying to publish using github pages but the page is blank. I've renamed the repository to my username.github.io, I'm on the master branch and the index.html file is in the root directory. The only answers I've found for this were for Apps built with Jekyll or create-react-app.
link to the repository- https://github.com/davez01d/davez01d.github.io
link to the page- https://davez01d.github.io/
Related
When trying to host my webpage with a three.js background, everything loads properly when hosted locally but as soon as I push it up to github pages nothing loads - just html.
I am using vite to package my code, and gh-pages to deploy the 'dist' folder to the hosted branch. I have tried changing the urls of all images and assets to '/image' and storing the images in a public folder inside the root folder, as vite recommends. I run
$ npm run build, and
$ npm run preview
and everything looks good. I run npm run deploy (I added a deploy script in package.json, deploy: 'gh-pages -d dist'), and then host the gh-pages branch on github pages and only the html shows up, and the console shows multiple 404: file not found errors.
Repo
The hosted code is on the gh-pages branch, if that hasn't been clear already.
The url to your JS and CSS files is wrong.
Your github page is trying to load the the JS from https://talmage89.github.io/assets/index.2e5bc2a5.js...
But it should be:
https://talmage89.github.io/ThreeJSDemo2/assets/index.2e5bc2a5.js.
The Vite documentation hss specific instructions for setting the base when hosting on Github Pages
I have developed a full angularjs web app that I need to Bower install or npm install it into another angularjs project. Do I need to bundle the whole app as one .js file e.g. templateCache.js that contains all the HTML codes in it or there is no need to bundle all into one .js but seperate index.css index.html index.js
I am new to github and webpage dev in general. I built a simple webpage (with html, css, and js) that I'm trying to publish in github.io
The website works when I open the index.html file from my local desktop. But when I push the exact folder / files to my github repository the Github Pages link produces a weird webpage.
Here is the link to my repository: link
Here is the link to my github IO webpage: https://pinzhi000.github.io/FSA_guessingGame/
What am I doing wrong?
Your index.html is in guessing-game-master folder.
Use this link https://pinzhi000.github.io/FSA_guessingGame/guessing-game-master/
I'm trying to add a vuejs project built using webpack in gituhub pages. I have created a repository.
renamed dist folder as a doc folder.
changed the settings-> github pages-> source to master-branch docs folder
this is the docs folder
Everything has done properly, the project is working fine when I'm running it in dev server. but when I pushed in github pages it is not working at all.
When I opened the link of the repository page i'm getting a blank window. I checked in the browser console.
I'm getting this error in browser:
.
Please find a solution for this please. More vue projects are there to upload and i'm unable to upload one at least.
I am trying to render my GitHub repo on the Publisher-Subscriber module with JavaScript using GitHub pages. The gh-pages branch looks fine. However, the mustache code does not render on my project on GitHub Pages. It looks like this :
GitHub Repository : https://github.com/ajhalthor/pubsub-application
Github Pages Repo for this project : https://ajhalthor.github.io/pubsub-application/
The GitHub Repository also has the node_modules folder, so it should be self sufficient. Mustache, jQuery & Bootstrap are included in this folder, so there are no external links or CDNs.
Main Question : Why isn't mustache rendering even though all paths are specified relative to the project's main folder?
Github pages uses a version of Jekyll that ignores node_modules folder by default.
According to this blog article. You can do the following:
Create an empty .nojekyll text file in the root of the gh-pages branch.
You can also refer to this announcement by github which talks about the update that is responsible for this behavior.