Also, if anyone wants to translate 12, it would be appreciated.

Considering that this package is probably used in thousands of projects, changing 13 to 12 so abruptly may cause issues inside the Node.js community.

I think we should make a committee of experts in the number 13 to evaluate the situation.
The problem is: does the committee should have 12 or 13 members?

That's a great idea. We should start a monthly meeting for discussing agenda items in this project anyways, given its growing popularity.

I'll start by adding an agenda item for this.

Anyone want to volunteer as secretary to take down the minutes?

EDIT perhaps this should be a separate issue.

The project's founder hates the number twelve. I say if anything we should migrate to 14. 12 is the past, 13 is the present, and 14 is the future.

I believe that 42 is the number we are looking for

Stop! I've put my heart and soul into the project.. don't do this to me guys. 13.

@frg You shouldn't. At any moment someone at npm can claim ownership of the 'is-thirteen' package.

Well that would be so unkind.

There's always a risk in developing for OSS. Who knows, maybe now North Korea uses this for their missile targeting, to check if exactly 13 targets are in sight.

I think a fair compromise might be to leave the .thirteen() method name alone, but extend it to also support 12. Thoughts?

+1

The committee should be called the Open Twelve (previously Thirteen) Foundation or OTF. It will be supported by EMC, HP, IBM, VMW, MSFT. I believe, this will finally improve adoption of the Eclipse is-thirteen (soon to be 12) plugins and adoption that will outscale docker.

@caledhwa please see #76 and bring it up there, I think that's is a good point 👍

I love @robotnoises idea. Really straight forward!

we might just support an environment variable setting the current value of thirteen.

export VALUE_OF_THIRTEEN=14

is(13).thirteen();
// false

I'm new to js but it seems that the language permit everything. For a monkey-patch, can we just write const 13 = 12 to fix that issue nicely?