Static assets

Help
1

Sorry for distributing, I am kind of new to vercel but

IMG_20241007_173134
IMG_20241007_1731341080×1955 332 KB

See the image , In the build step my script created some files in the build step but they are not included in the static assets , how can I fix this?

2

Hi @educatedsuddenbucket. It looks like the files are being added to the /public directory, so that would need to be included in the address path. For example, my-awesome-site.com/public/1 rather than my-awesome-site.com/1

You could configure rewrites to remove the /public segment from the path. Or you could change the way your project builds these files.

If you need help setting it up, please share a minimal reproducible example so we can make specific recommendations that will work for your repo. :slightly_smiling_face:

3

I cannot provide a reproducible example here because my code uses the GitHub api,but I can give you a reproducible example somewhere where conversation is private , but here is some info
My vercel.json is this

{
  "version": 2,
  "builds": [
    {
      "src": "server.js",
      "use": "@vercel/node"
    },
    {
      "src": "public/**/*",
      "use": "@vercel/static"
    }
  ],
  "routes": [
    {
      "src": "/api/(.*)",
      "dest": "/server.js"
    },
    {
      "src": "/create",
      "dest": "/server.js"
    },
    {
      "src": "/(.*)",
      "dest": "/public/$1"
    }
  ],
  "regions": ["bom1"]
}

I have tried to access my html with these url paths
/1 , /1.html , /public/1 , /public/1.html

Also the other html and asets u see like manage.html , manage.js , work and were pre included in the code and were not generated through build

4

It’s been a few days. Thanks for your patience. I hope you found a solution and you’re not still stuck.

If you still need help, a minimal reproducible example would let us both work from the same code so we can debug this together. If you can share one, I’m happy to take a closer look.

If you prefer to debug on your own, I find the Output info on the Source tab very helpful. That will show you the file structure as it is deployed so you can see which paths exist. I also wrote a more detailed post to help with 404 errors. That’s also worth a read if you’re still having trouble with this.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.