Static folder in route group isn't picked up by Vercel build

Help
1

Is it possible to make Next.js keep the contents of that folder?

I’m working on implementing a Sanity’s new Create feature. It requires couple of files to be in a specific location. I’m using version 14.3.2 of Next.js and the app router. My app folder structure looks like this:

├── app
│   ├── (studio)
│   │   ├── admin
│   │   │   ├── [[...index]]
│   │   │   │   └── page.tsx
│   │   │   └── static
│   │   │       └── .gitkeep
│   │   │     
...

On build, a script runs and generates two JSON files in the /app/(studio)/admin/static directory, and I’ve confirmed the files are generated during the build by listing the directory contents in the build script. The build logs show the files were created:

image
image1568×416 56.8 KB

When checking the build’s files, though, the json files in the screenshot above don’t exist. This is what shows up in the deployment’s source/output files:

image
image2396×1692 220 KB

Here’s an excerpt of my run script that generates those files:

"scripts": {
    "prebuild": "npm run typegen && npm run extract-manifest",
    "build": "next build",
    "start": "next start",
    "extract-manifest": "cd src/sanity && sanity manifest extract --path '../app/(studio)/admin/static' && ls -all '../app/(studio)/admin/static'",
    "typegen": "cd src/sanity && sanity schema extract --path ../../sanity-schemas.json && sanity typegen generate"
  },

I’m not sure if this is related to the route group, opitonal catch-all, or something else entirely. Ultimately I need to be able to populate the admin/static folder with the Create json files created during build. Any tips on how to achieve this?

Thanks!

Edit:
I’ve added the following to my next config and am testing things now.

  experimental: {
    outputFileTracingIncludes: {
      '/admin/static': ['./src/app/(studio)/admin/static/**/*'],
    },
  },
2

Hi, @rcmaples! Welcome to the Vercel Community :smile:

It’s been a couple of days since you posted this, did you manage to find your solution?

3

No, not yet :frowning:

I x-posted in the next.js community discord as well, but haven’t managed to get anywhere.