add .npmignore

[necccc]

Hi 👋

I’ve been doing a little research for a conference talk on how npm package size relates to their content, and your package was one in the several ones that were flagged by my scripts. It has an outstanding weekly download count on npm and relatively large content that is not related directly to the package functionality.

I've added some files and folders to an .npmignore file, so they won't get packaged next time you release it on npm.

Thanks, and have a great day!

[mourner]

Thank you, good catch! Instead of adding an .npmignore, can we add a files field in package.json instead?

[necccc]

sure thing, you can do both, note that anything in 'files' will have precedence over the content of .npmignore

[mourner]

@necccc I mean, can we do that in this PR? I prefer the package.json approach that doesn't clutter the repo with additional files and is easier to maintain.

[necccc]

I'll try, the quickest way was just to ignore these, for the "files" field I have to check what exactly your package needs.

[mourner]

@necccc I think only the bin/pixelmatch, everything else should be included automatically. We can
confirm with npm publish --dry-run.

[mourner]

Fixed in e19712b