-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't publish the benchmark #21
Comments
@userpixel Good call, let's fix that. |
So, I guess this is not enough? Lines 11 to 15 in 67f6603
|
The benchmarks are not published to npm as I'm using the Case solved. |
I like your opt-in approach. According to https://docs.npmjs.com/files/package.json#files:
|
The
./bench
dir contains a benchmarking code that is not part of the module strictly speaking so it doesn't need to be published. On the same line of argument we can skip publishing the tests as well.Suggested solution
Add an
.npmignore
file to the root with this content:That's all! 👍
The text was updated successfully, but these errors were encountered: