`attw --pack` is incorrect for sub-pkg in monorepo

[zanminkian]

Reproduce:

0. Enable corepack
1. git clone https://github.com/zanminkian/fenge.git
2. pnpm i
3. npm pack ./packages/eslint-config && attw fenge-eslint-config-0.0.0.tgz print what I expected ✅.
4. attw --pack ./packages/eslint-config print information different from step 3 ❌.

[kirkwaiblinger]

I encountered this as well, while working on typescript-eslint/typescript-eslint#12437, and I believe it may be partially due to pnpm/pnpm#12560, where I observed that npm pack and pnpm pack have different behavior regarding gitignored files in a sub package.

I guess the underlying cause here, though, is that the attw --pack specifically uses npm pack, even if it's not an npm repo. This has other observable consequences as well, for example deps in the package.json still have things like workspace: and catalog: when using npm pack in a pnpm repo, whereas pnpm pack resolves those to the actual deps. Maybe that specific example doesn't matter for any of the checks that attw does, but perhaps there are other observable discrepancies that do matter 🤷.

Maybe attw just should document that --pack only is expected/guaranteed to work with npm repos, and you should pack the tarball yourself if it's a different kind of repo? Or maybe --pack-with-pnpm/--pack-with-yarn options should be added?

[kirkwaiblinger]

Oh, it looks like maybe non-npm support once was attempted and was reverted? #180