We Keep Coding

Problem with loading .gltf files in Github pages of my React Three.js app with Vite

I deployed my React Three.js with Vite app in Github pages, and I can't get it running on a live server - https://thehero9.github.io/ThreeJsReactFiber/
This here is the code in my repo - https://github.com/TheHero9/ThreeJsReactFiber
I have no trouble with the app locally, you can try cloning it with git, then run:
npm install
npm run dev
In order to check how it works locally.
I think the .gltf files are not being loaded correctly due to a problem with the file paths or the loading code. Please, can you help us and check whether you can find why the .gltf files are not loading?
Errors:
Everything is loaded properly on a local server:
[3]: https://i.stack.imgur.com/xV31l.jpg

Github pages responds with 404 error for three.js canvas and imports

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

How to run Node app locally from Github repo?

I want to run this https://github.com/supernoir/heroines-of-science locally.
I did the following steps
Cloned the app locally
Then did npm install to download all the dependencies
Opened the app folder and executed node server.js
But getting Cannot Get / when opened the webpage.
Any help would be helpful.

How to deploy react, next js + express js app to netlify?

I am trying to deploy my app to netlify which is created by using react, next js, and express js.
There is no error in netlify console Despite this, site is not being live.
Here are my package.json scripts.
Here are my variable environments on netlify.
Here are my build settings to netlify.
Please can anyone tell me where I am making mistakes?

npm run build
then drag and drop this build folder but netlify doesnt support server i think firebase is the best option or herokuu too

Vue.js PWA Plugin not loading service-worker.js when deployed to subfolder (Github Pages)

I used the Vue CLI to create a new Vue project, and selected PWA support when using 'vue create'.
I also used the vue-gh-pages plugin to deploy the app to a github pages URL.
The problem is that it's attempting to load
http://myusername.github.io/service-worker.js
..instead of:
http://myusername.github.io/app-name/service-worker.js
Inside of /src/registerServiceWorker.js I can noticed:
register(`${process.env.BASE_URL}service-worker.js`, {
But when I attempt to set the BASE_URL in vue.config.js with:
module.exports = {
baseUrl: '/app-name/'
}
..it breaks the links from all of the other scripts.
The app works when I run it locally, along with the PWA support. Anyone know how to get this to work with sub folders / github pages?
Thanks

I think you are forgetting to build your project before you deploy it. If you are running a Vue CLI that uses a build process, you should be running npm run build which will generate a dist folder that has all your resources as a static bundle.
You should commit that to your gh-pages branch and serve that instead.
I'm saying this because process.env.BASE_URL is something that the node.js side of things understands. GitHub pages won't be populating that for you at runtime since it only serves content statically.