fix(prettier-config): avoid bundling TS build info and deps

[mcous]

Overview

Small tweak to the publish settings for the prettier configs after examining the published bundles

1. ci: release with pnpm publish instead of action #48
2. feat(prettier-config)!: split configs and use direct dependencies #49
3. 🌿 fix(prettier-config): avoid bundling TS build info and deps #51
4. feat(eslint-config)!: split config packages #50
5. TODO: Update ESLint packages to use ESLint v9 and flat configs

Change log

Switched from the files allowlist to an .npmignore blocklist since it's (apparently for my brain) a little less error prone

• Remove **/* from files to prevent bundling node_modules into the tarball
• Ignore *.tsbuildinfo

[zaporter-work]

Does npm implicitly not bundle folders named node_modules if it isn't in the included files? I notice it's not in the npmignore

[mcous]

Does npm implicitly not bundle folders named node_modules if it isn't in the included files? I notice it's not in the npmignore

Yup, there's a set of things that are always ignored by default: https://docs.npmjs.com/cli/v8/using-npm/developers#keeping-files-out-of-your-package.

Somehow, adding **/* told npm / pnpm to turn @viamrobotics/prettier-config into a bundledDependency of @viamrobotics/prettier-config-svelte. I'm not sure if this is an npm behavior or something specific to pnpm workspaces, but I hadn't seen it before. Regardless, a simple .npmignore gets things to where I expected them