Copy static files about tsup

[NuroDev]

Would it be possible / worth updating the publicDir property to additionally accept an array or record like entry so we can manually map out multiple public / static asset (directories) that need to be copied.

Something like this:

import { defineConfig } from 'tsup';

export default defineConfig({
	publicDir: [
		'./src/assets/',
		'./src/static/'
	]
});

// OR

export default defineConfig({
	publicDir: {
		'./src/assets/': './dist/assets/',
		'./src/static/': ({ output }) => `${output}/static/`
	}
});

In theory I thought a work around for this would be to return an array of configs & just have multiple publicDir's that way but with no entry point it does not work.

While --onSuccess "cp -a public/. dist" works, there is a few things that aren't ideal about it:

• Desync with your output directory name (Though this could be fixed with a template string)
• CLI exec is not ideal & would be better if it was all done pragmatically. In the same way rm -rf ./dist/ works, but not on Windows systems so people often use rimraf to add platform agnostic support.

[egoist]

This can be achieved with the onSuccess option, like --onSuccess "cp -a public/. dist" which copies everything inside public folder to your dist folder.

[domdomegg]

The --publicDir argument will copy everything in the public folder into the dist folder.

https://tsup.egoist.dev/#copy-files-to-output-directory

[niaxi]

How are folks dealing with this currently? Wrapper build script? Example?

[zheeeng]

Any progress on this feature?

[eric-burel]

Something I've noticed, cp public/ dist/ && tsup will somehow delete the files copied in dist/public/. However I found no mention of "public" in the doc. The solution is to do the copy after Tsup has built but that's kinda weird.