Support multiple static asset dirs by allowing string arrays for `config.kit.files.assets`

[janosh]

Describe the problem

I'd like to get static assets from multiple locations. In this example the SvelteKit site is inside the site/ directory as part of a bigger project and I'd like to use static assets from assets/ and site/static/.

.
├── assets
│   ├── ...
└── site
    ├── src
    ├── static
    └── ...

Describe the proposed solution

config.kit.files.assets could support arrays:

// svelte.config.jg

export default {
  kit: {
    adapter: adapter(),

    files: {
      assets:[ `../assets`, `./static` ],
    },
  },
}

This currently raises

config.kit.files.assets should be a string, if specified

Alternatives considered

Create an alias of assets/ in site/static/. It works but feels hacky.

Importance

nice to have

Additional Information

No response

[jochemvogel]

Would love to see this. I'm trying to exclude the static/img folder from the { files } in my service worker, because of the size.

I now do it with a workaround, but feels not very natural. Is there another solution for this problem?

Workaround: const cachedFiles = files.filter(file => !file.startsWith('/img');

[alexanderl19]

Would also love to see this. It looks like vite only supports one public folder, so this might be a vite limitation?

[fvilers]

Would need that too !

[WillsterJohnson]

this would be very useful in a multisite monorepo, where shared assets are stored in {root}/assets and site specific assets are stored in {root}/apps/appName/assets.

Currently I'm creating a symlink such that {root}/apps/appName/assets/global -> ../../../assets