include only the lib/ folder in the package, exclude tests and examples

[necccc]

This npm module has 56kByte overhead with tests and examples, not needed for the functionality of the module itself. Fixed this by adding the 'files' field in the package.json.

[ljharb]

No. The files key is dangerous; if a new file is added to the package but omitted from this list, downstream consumers would break.

Separately, the tests are supposed to be published to npm. npm explore foo && npm install && npm test should always work.

[ljharb]

Duplicate of #175. Duplicate of #132. Duplicate of #128. Duplicate of #99. Duplicate of #59. Duplicate of #44.

[necccc]

Beg to differ, whenever one is contributing to a package, usually uses the git repo - its logical if you need pull requests.

This approach results in approx 16kBytes of content on average for every package in npm not related to the functionality of the package. (based on my recent research) - it would be interesting to see actually how many ppl use the explore command.

[necccc]

But you're the maintainer so it's your decision.

[ljharb]

You can’t use the git repo if you installed, and are later working offline.