Update .npmignore

[pkuczynski]

No description provided.

[lveneris]

See #205
This removes the need for an .npmignore altogether, as it is inclusive, rather than exclusive.

[pkuczynski]

Yeah, it all depends on what one prefers: whitelisting or blacklisting :) There are pros and cons for both.

[lveneris]

@pkuczynski Ultimately, for bundling, whitelisting is the way to go. If you had to package someone's order for delivery in a warehouse, would you be given a list of things they haven't ordered or a list of things they have? I appreciate the sentiment, though :)

[alexei]

What problem does this address?

[lveneris]

@alexei It is unnecessary now, due to my PR. However, if you wish to investigate this too, that's fine.

[pkuczynski]

@alexei would you be keen moving forward or should I just close this PR?

[lveneris]

I believe it is safe to assume the project has been abandoned, since the last commit was 3 years ago.

It is deeply unfortunate that the JS ecosystem is as rigid as it is. Ancient unmaintained and wholly unnecessary packages are still getting 39 million weekly downloads. The package itself should be given a depreciation warning.

[pkuczynski]

Yeah, probably, but wanted to be kind before I delete my fork...