To be clear, it looks like the problem is that we are publishing the spec file.

This can also be solved in a different way, where test files are in a specific test folder, which is not included in the files list that is published to npm. After a lot of testing this single line change seems the most elegant.

Dumb question, but can we use the NPM config to ignore these files? Last I recall you couldn't combine .npmignore with files, or put negations in files, but those would be a tiny bit nicer.

An .npmignore does work, ala dist*/*.spec.*, but then it overrides anything in .gitignore when it comes to publishing.

Since the package is whitelisting with the files field of package.json, it's less of a concern, but still something to keep in mind.

Grrr, I've written, rewritten, and deleted this comment several times now. I'm not having any luck actually with .gitignore or .npmignore.

@jonchurch Thanks for exploring! Sorry to put you through that. Let's merge and we can release as is.

Thanks to @StephenTangCook for asking the question!

We may need to revert this or do additional work. I realized the other week that by excluding these files, it’s not actually using the right settings for type checking. Not a problem right now, but we should probably have a specific build config instead of changing this one.