Headers tarball way too big for 17.x+

[rvagg]

Version

17.x

Platform

headers

Subsystem

src

What steps will reproduce the bug?

Continuing on from nodejs/build#2695 (copying my latest comment there):

root@test-digitalocean-ubuntu1804-x64-1:/home/iojs/.cache/node-gyp/18.0.0-nightly20220222c071bd581a/include/node/openssl/archs# ls
BSD-x86     VC-WIN64-ARM  aix64-gcc       darwin64-arm64-cc   linux-armv4  linux-ppc64    linux32-s390x    linux64-s390x
BSD-x86_64  VC-WIN64A     aix64-gcc-as    darwin64-x86_64-cc  linux-elf    linux-ppc64le  linux64-mips64   solaris-x86-gcc
VC-WIN32    aix-gcc       darwin-i386-cc  linux-aarch64       linux-ppc    linux-x86_64   linux64-riscv64  solaris64-x86_64-gcc
root@test-digitalocean-ubuntu1804-x64-1:/home/iojs/.cache/node-gyp/18.0.0-nightly20220222c071bd581a/include/node/openssl/archs# du -sh .
61M     .

Also https://nodejs.org/download/release/latest-v16.x/

node-v16.14.0-headers.tar.gz                       08-Feb-2022 12:46              560771

vs

https://nodejs.org/download/release/latest-v17.x/

node-v17.6.0-headers.tar.gz                        22-Feb-2022 22:38             9923593

on the latest 18.x nightly it's even up to 10028309 bytes now! These files were supposed to be small and lean for node-gyp to download and use to compile addons. They're now the size of 0.12 binary tarballs!

I'm not sure of the exact solution to this, I don't know how much of these arch specific headers are required, but this is neither sustainable for our infra not ideal for users.

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

Additional information

No response

[rvagg]

cc @nodejs/crypto I guess

[richardlau]

Duplicate of #42081.

[rvagg]

sorry, dupe of #42081 I guess