chore: remove tests from package build

[opravil-jan]

Hi,
we have problem with out vulnerability management which scans package.json files and try to find vulnerabilities. We use PRISMA from Palo Alto. Problem is that you are trying to test validity of package.json file in test which is not well formatted package.json file. Our vulnerability management has problem with this invalid package.json. I think it is better not to include tests to build of npm package.

Thanks
Jan

[ljharb]

This would be a breaking change.

This is quite intentional. Those files must be included.

Tests should be published with every package, so that npm explore foo && npm install && npm test always works.

Duplicate of #239. Duplicate of #235. Duplicate of #58. Duplicate of #44. See #105 (comment).

If PRISMA can’t handle an invalid package.json that’s nested inside a package (where it shouldn’t even be checking in the first place), i suggest reporting the bug to it directly.

[opravil-jan]

I do not see, how would be a BC. Nobody is saying to remove tests from repository. I do not see any reason to have tests included in package when I install it by "npm install resolve" and the package is placed into node_modules

[ljharb]

Because consumers - including myself - rely on being able to run the tests of the installed package. Whether you see the reason is irrelevant; the reason exists, and that’s why all 300+ of my packages publish their tests and will continue to do so.