From c67310fe292bb8902b38687bc94e1111182d3414 Mon Sep 17 00:00:00 2001 From: Robert Kieffer Date: Thu, 6 Jun 2019 06:56:52 -0700 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1770698..c8f9bf0 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,8 @@ # ![image](https://user-images.githubusercontent.com/164050/52737878-42886600-2f82-11e9-81de-c750db7b4ac3.png) This package is not actively maintained -`int64` was a workaround JS' lack of support for Int64 data types. Somewhat to my surprise, people have found it useful. However, [BigInt](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt)s are becoming a thing. If you're writing new code, please use `BigInt`s. +`int64` was a workaround JS' lack of support for Int64 data types. Somewhat to my surprise, people have found it useful. However, it looks like [BigInt](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt)s will soon be a formally accepted feature, obsoleting the need for this package. -That said, if a trustworthy organization or individual would like to take over, I'm happy to hand this off. Please contact me at [robert@broofa.com](mailto:robert@broofa.com) if you're interested. Otherwise I'll be npm-deprecating this at some future date. +If a trustworthy organization or individual would like to take over as maintainer, I'm happy to hand this off. Please contact me at [robert@broofa.com](mailto:robert@broofa.com) if you're interested. Otherwise I'll be npm-deprecating this at some future date. # int64