🚀 Feature: Remove sourcemap: true from tsup.config.ts

[JoshuaKGoldberg]

Bug Report Checklist

• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

For many years now, I've tried to publish sourcemaps in all projects I publish to npm. The idea was that it would be nice for folks debugging through the code to see the source, including pre-transpiled syntax sugar and TypeScript types.

More recently I've seen packages move away from sourcemaps:

• Bug: packages incorrectly publishes .js.map breaking stack traces typescript-eslint/typescript-eslint#9352: noting that sourcemaps add a lot to the typescript-eslint published output size, and aren't always useful or even correct
• 🐛 Bug: Package size is a whopping 1.2MB ts-api-utils#573 -> build: shrink size of bundle ts-api-utils#576: similarly, removing them from ts-api-utils dropped the built size a good bit

I'm personally now in favor of removing sourcemaps from the default tsup.config.ts in CTA and its templates. But just to be safe, I'll leave this issue with status: in discussion for a while. If anybody knows of reasons to do this or not to do this, please post! 🙂

Additional Info

Note that this involves editing both the repo's tsup.config.ts and the blockTsup that generates it.

🎁

[JoshuaKGoldberg]

It's been a couple of weeks and I haven't changed my mind. Also typescript-eslint/typescript-eslint#9352 (comment) shows a lot of other projects not shipping sourcemaps. Accepting PRs.