P5.js sketch not shown in Vercel

My project:
Vercel CLI 39.1.3
:mag: Inspect: pacman2024windows – Deployment Overview – Vercel [4s]
:white_check_mark: Preview: https://pacman2024windows-itozll8zi-ejgutierrez74s-projects.vercel.app [4s]

In local Vite the project and sketch is show right.
Deploy in Vercel i cant see the sketch

Watch the project in local vite and works ok.
Deploy to Vercel and doesnt work

My project:

My log:
[22:12:38.436] Running build in Washington, D.C., USA (East) – iad1
[22:12:38.578] Retrieving list of deployment files...
[22:12:38.892] Previous build cache not available
[22:12:39.025] Downloading 136 deployment files...
[22:12:40.296] Running "vercel build"
[22:12:42.034] Vercel CLI 39.1.3
[22:12:43.075] Installing dependencies...
[22:12:46.604] npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
[22:12:46.800] npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[22:12:47.001] npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
[22:12:47.350] npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
[22:12:47.438] npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
[22:12:47.570] npm warn deprecated eslint-plugin-ecmascript-compat@3.2.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
[22:12:48.618] npm warn deprecated eslint@8.57.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
[22:12:49.123] 
[22:12:49.124] added 320 packages in 6s
[22:12:49.124] 
[22:12:49.124] 120 packages are looking for funding
[22:12:49.125]   run `npm fund` for details
[22:12:49.150] Running "npm run build"
[22:12:49.281] 
[22:12:49.283] > Practica Pacman2024@0.0.1 build
[22:12:49.283] > vite build
[22:12:49.283] 
[22:12:50.173] e[36mvite v6.0.2 e[32mbuilding for production...e[36me[39m
[22:12:50.175] (node:134) ExperimentalWarning: CommonJS module /vercel/path0/vite.config.js is loading ES Module /vercel/path0/node_modules/vite/dist/node/index.js using require().
[22:12:50.175] Support for loading ES Module in require() is an experimental feature and might change at any time
[22:12:50.175] (Use `node --trace-warnings ...` to show where the warning was created)
[22:12:50.234] <script src="js/libraries/p5.min.js"> in "/index.html" can't be bundled without type="module" attribute
[22:12:50.235] <script src="js/sketch.js"> in "/index.html" can't be bundled without type="module" attribute
[22:12:50.255] transforming...
[22:12:50.261] e[32m✓e[39m 3 modules transformed.
[22:12:50.282] rendering chunks...
[22:12:50.287] computing gzip size...
[22:12:50.291] e[2mdist/e[22me[2massets/e[22me[32msite-BxrbV1h7.webmanifest  e[39me[1me[2m0.23 kBe[22me[1me[22m
[22:12:50.292] e[2mdist/e[22me[2massets/e[22me[32micon-CrLf0eJB.svg          e[39me[1me[2m0.43 kBe[22me[1me[22me[2m │ gzip: 0.30 kBe[22m
[22:12:50.292] e[2mdist/e[22me[2massets/e[22me[32mfavicon-tl4dpFnO.ico       e[39me[1me[2m0.77 kBe[22me[1me[22m
[22:12:50.292] e[2mdist/e[22me[32mindex.html                        e[39me[1me[2m1.44 kBe[22me[1me[22me[2m │ gzip: 0.59 kBe[22m
[22:12:50.297] e[2mdist/e[22me[2massets/e[22me[32micon-ijzhoTP6.png          e[39me[1me[2m4.03 kBe[22me[1me[22m
[22:12:50.298] e[2mdist/e[22me[2massets/e[22me[35mindex-D3hqRGbY.css         e[39me[1me[2m3.20 kBe[22me[1me[22me[2m │ gzip: 1.28 kBe[22m
[22:12:50.298] e[32m✓ built in 86mse[39m
[22:12:50.369] Build Completed in /vercel/output [7s]
[22:12:50.406] Deploying outputs...
[22:12:54.084] 
[22:12:54.461] Deployment completed
[22:12:58.893] Uploading build cache [14.38 MB]...
[22:12:59.180] Build cache uploaded: 286.407ms

I dont have any vercel.json file nor in my local repository nor in vercel. I installed vercel in local with pnpm i -g vercel and executed vercel to deploy following a little questionary…

Errors in console_


GEThttps://pacman2024windows.vercel.app/js/libraries/p5.min.js[HTTP/2 404 104ms]

GEThttps://pacman2024windows.vercel.app/js/sketch.js[HTTP/2 404 82ms]

GEThttps://ejgutierrez.github.io/Pacman2024Windows/assets/index-D3hqRGbY.cssCORS Missing Allow Origin

Solicitud desde otro origen bloqueada: la política de mismo origen impide leer el recurso remoto en https://ejgutierrez.github.io/Pacman2024Windows/assets/index-D3hqRGbY.css (razón: falta la cabecera CORS 'Access-Control-Allow-Origin'). Código de estado: 404.

Ha fallado la carga del <script> con origen "https://pacman2024windows.vercel.app/js/libraries/p5.min.js". [pacman2024windows.vercel.app:24:42](https://pacman2024windows.vercel.app/)

GEThttps://pacman2024windows.vercel.app/js/sketch.js[HTTP/2 404 96ms]

Ha fallado la carga del <script> con origen "https://pacman2024windows.vercel.app/js/sketch.js". [pacman2024windows.vercel.app:28:32](https://pacman2024windows.vercel.app/)

GEThttps://ejgutierrez.github.io/Pacman2024Windows/assets/index-D3hqRGbY.cssCORS Missing Allow Origin

Solicitud desde otro origen bloqueada: la política de mismo origen impide leer el recurso remoto en https://ejgutierrez.github.io/Pacman2024Windows/assets/index-D3hqRGbY.css (razón: falta la cabecera CORS 'Access-Control-Allow-Origin'). Código de estado: 404.

GEThttps://ejgutierrez.github.io/Pacman2024Windows/assets/icon-ijzhoTP6.pngNS_BINDING_ABORTED

GEThttps://ejgutierrez.github.io/Pacman2024Windows/assets/icon-CrLf0eJB.svgNS_BINDING_ABORTED

A resource is blocked by OpaqueResponseBlocking, please check browser console for details. [icon-CrLf0eJB.svg](https://ejgutierrez.github.io/Pacman2024Windows/assets/icon-CrLf0eJB.svg)

A resource is blocked by OpaqueResponseBlocking, please check browser console for details. [icon-ijzhoTP6.png](https://ejgutierrez.github.io/Pacman2024Windows/assets/icon-ijzhoTP6.png)

La cookie “__vercel_live_token” ha sido rechazada porque se encuentra en un contexto de sitios cruzados y su “SameSite” es “Lax” o “Strict”. [validate](https://vercel.live/login/validate?hostname=pacman2024windows.vercel.app&deploymentId=)

La cookie “__vercel_live_token” ha sido rechazada porque se encuentra en un contexto de sitios cruzados y su “SameSite” es “Lax” o “Strict”.

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.