Output Based on Filename?

[Crisfole]

I'm trying to build a nice tsup.config.ts/package.json combination for releasing NPM packages. I'd like:

import { defineConfig } from 'tsup'

export default defineConfig({
	entry: [
		"src/*.ts",
		"src/*/+(index|worker|*.worker).ts",
	],
	dts: true,
	format: 'esm',
	splitting: false,
	sourcemap: true,
	clean: true,
})

to build the src/*.ts into dist/*/index.mjs (basically wrapping into an index) so the following "exports" and "files" combination in package.json works neatly:

{
  "//": "...",
  "exports": {
    ".": {
      "import": "./dist/index.mjs",
      "types": "./dist/index.d.ts"
    },
    "./*": {
      "import": "./dist/*/index.mjs",
      "types": "./dist/*/index.d.ts"
    }
  },
  "files": [
    "dist/**/*",
    "package.json"
  ],
  "//": "...",
}

This should result in every top-level foo.ts file and ever second-level bar/index.ts, bar/worker.ts and bar/foobar.worker.ts getting built in dist and becoming importable like so:

import { Foo } from "@scope/package/foo";
import { Bar } from "@scope/package/bar";

Package exports do not handle multiple ways to resolve a single export (I can't say, "check dist/foo.mjs, then dist/foo/index.mjs if that's missing"), so this falls on tsup or even worse, me, to setup the dist folder correctly.

Does TSUP support a function like Rollup's entryFileNames? I've poked aroudn the code base and can't seem to find anything like it...

[Crisfole]

OK, so as tradition requires, I figured this out shortly after posting this.

tsup accepts multiple configs and allows passing esbuildOptions. The solution:

import { defineConfig } from 'tsup'

export default defineConfig([
	{
		entry: [
			"src/*.ts",
		],
		dts: true,
		format: 'esm',
		splitting: false,
		sourcemap: true,
		clean: true,
		esbuildOptions(opts, ctx) {
			opts.entryNames = "[dir]/[name]/index"
		}
	},
	{
		entry: [
			"src/*/+(index|worker|*.worker).ts",
		],
		dts: true,
		format: 'esm',
		splitting: false,
		sourcemap: true,
		clean: true,
	}
])

[RodrigoNovais]

Do you know if I can somehow skip the /dist/ part of importing
I thought exports would do that but it seems I got it wrong

[Crisfole]

Exports only works if your module resolution is set to NodeNext…it’s still s as super young spec.

[SonNg2k]

@Crisfole By the way, do you know how to change the names of the output files from app.ts to outputCustomName.js like below:

import { defineConfig, type Options } from 'tsup';

export default defineConfig((options: Options) => ({
  entry: ['src/templates/customers/*/app.ts'], // files should be named as "*.js" in the ./build folder
  noExternal: [/^@amest\//],
  clean: true,
  format: 'esm',
  shims: true,
  outDir: 'build',
  treeshake: true,
  ...options,
}));

[Crisfole]

Nope…I don’t. I imagine there’s a way though

[brianjenkins94]

Interesting that you can provide an array of configs to defineConfig, but build doesn't accept an array of configs.

It must spawn a new process for each config?