Whenever i deploy my page, it publishes but it says "you have followed a broken link"

I’m very new to computer science so I decided to ask for help here. I have deployed multiple forks from GitHub and every time I have it shows the “you have followed a broken link” message. My website is https://comfy-figolla-6b8bca.netlify.app/ my log is
6:49:47 PM: build-image version: 68a2c262fa3c95a08a1716b8dde8fba0e332ec73 (focal)
6:49:47 PM: buildbot version: 68a2c262fa3c95a08a1716b8dde8fba0e332ec73
6:49:48 PM: Fetching cached dependencies
6:49:48 PM: Failed to fetch cache, continuing with build
6:49:48 PM: Starting to prepare the repo for build
6:49:48 PM: No cached dependencies found. Cloning fresh repo
6:49:48 PM: git clone --filter=blob:none GitHub - jack9192/Nebula: Nebula Web is a stunning and sleek web proxy with support for hundreds of popular sites.
6:49:48 PM: Preparing Git Reference refs/heads/main
6:49:49 PM: Parsing package.json dependencies
6:49:50 PM: Starting to install dependencies
6:49:50 PM: Python version set to 3.8
6:49:50 PM: Attempting Ruby version 2.7.2, read from environment
6:49:51 PM: Using Ruby version 2.7.2
6:49:51 PM: Started restoring cached go cache
6:49:51 PM: Finished restoring cached go cache
6:49:51 PM: Installing Go version 1.19.5 (requested 1.19.5)
6:49:56 PM: go version go1.19.5 linux/amd64
6:49:56 PM: Using PHP version 8.0
6:49:57 PM: v16.20.0 is already installed.
6:49:58 PM: Now using node v16.20.0 (npm v8.19.4)
6:49:58 PM: Enabling Node.js Corepack
6:49:58 PM: Started restoring cached build plugins
6:49:58 PM: Finished restoring cached build plugins
6:49:58 PM: Started restoring cached corepack dependencies
6:49:58 PM: Finished restoring cached corepack dependencies
6:49:58 PM: No npm workspaces detected
6:49:58 PM: Started restoring cached node modules
6:49:58 PM: Finished restoring cached node modules
6:49:58 PM: Installing npm packages using npm version 8.19.4
6:49:58 PM: npm WARN EBADENGINE Unsupported engine {
6:49:58 PM: npm WARN EBADENGINE package: ‘nebula-web@7.11.6’,
6:49:58 PM: npm WARN EBADENGINE required: { node: ‘>=18’ },
6:49:58 PM: npm WARN EBADENGINE current: { node: ‘v16.20.0’, npm: ‘8.19.4’ }
6:49:58 PM: npm WARN EBADENGINE }
6:49:58 PM: npm WARN EBADENGINE Unsupported engine {
6:49:58 PM: npm WARN EBADENGINE package: ‘@tomphttp/bare-server-node@1.2.3’,
6:49:58 PM: npm WARN EBADENGINE required: { node: ‘>=18.0.0’ },
6:49:58 PM: npm WARN EBADENGINE current: { node: ‘v16.20.0’, npm: ‘8.19.4’ }
6:49:58 PM: npm WARN EBADENGINE }
6:50:00 PM: added 149 packages, and audited 150 packages in 2s
6:50:00 PM: 13 packages are looking for funding
6:50:00 PM: run npm fund for details
6:50:00 PM: found 0 vulnerabilities
6:50:00 PM: npm packages installed
6:50:00 PM: Install dependencies script success
6:50:00 PM: No build steps found, continuing to publishing
6:50:00 PM: Starting to deploy site from ‘/’
6:50:00 PM: Calculating files to upload
6:50:00 PM: 0 new files to upload
6:50:00 PM: 0 new functions to upload
6:50:00 PM: Starting post processing
6:50:00 PM: Section completed: deploying
6:50:00 PM: Section completed: building
6:50:00 PM: Uploading Cache of size 1.3MB
6:50:00 PM: Post processing - HTML
6:50:00 PM: Section completed: cleanup
6:50:00 PM: Finished processing build request in 12.793s
6:50:00 PM: Post processing - header rules
6:50:01 PM: Post processing - redirect rules
6:50:01 PM: Post processing done
6:50:01 PM: Section completed: postprocessing
6:50:01 PM: Site is live :sparkles:

As shown in the line above, you are deploying from the repository root. So all the files in the repository as deployed, such as app.js.

As this is a Node.js project which only contains a start script, it is not a project that will work on Netlify as outlined in this support guide