- Предыдущие версии
- Ищете последнюю версию ветки версии?
- Node.js (64-bit)
- Saved searches
- Use saved searches to filter your results more quickly
- License
- broofa/node-int64
- Name already in use
- Sign In Required
- Launching GitHub Desktop
- Launching GitHub Desktop
- Launching Xcode
- Launching Visual Studio Code
- Latest commit
- Git stats
- Files
- README.md
- About
- Previous Releases
- Looking for latest release of a version branch?
Предыдущие версии
Релизы от 1.x до 3.x выходили под именем «io.js», так как они были частью форка io.js. Начиная с Node.js 4.0.0, предыдущие версии io.js перешли с Node.js 0.12.x в унифицированные версии Node.js.
Ищете последнюю версию ветки версии?
| Version | LTS | Date | V8 | npm | NODE_MODULE_VERSION[1] | |
| Node.js 20.4.0 | 2023-07-04 | 11.3.244.8 | 9.7.2 | 115 | ReleasesСписок измененийДокументация | |
| Node.js 19.9.0 | 2023-04-10 | 10.8.168.25 | 9.6.3 | 111 | ReleasesСписок измененийДокументация | |
| Node.js 18.17.0 | Hydrogen | 2023-07-18 | 10.2.154.26 | 9.6.7 | 108 | ReleasesСписок измененийДокументация |
| Node.js 17.9.1 | 2022-06-01 | 9.6.180.15 | 8.11.0 | 102 | ReleasesСписок измененийДокументация | |
| Node.js 16.20.1 | Gallium | 2023-06-20 | 9.4.146.26 | 8.19.4 | 93 | ReleasesСписок измененийДокументация |
| Node.js 15.14.0 | 2021-04-06 | 8.6.395.17 | 7.7.6 | 88 | ReleasesСписок измененийДокументация | |
| Node.js 14.21.3 | Fermium | 2023-02-16 | 8.4.371.23 | 6.14.18 | 83 | ReleasesСписок измененийДокументация |
| Node.js 13.14.0 | 2020-04-29 | 7.9.317.25 | 6.14.4 | 79 | ReleasesСписок измененийДокументация | |
| Node.js 12.22.12 | Erbium | 2022-04-05 | 7.8.279.23 | 6.14.16 | 72 | ReleasesСписок измененийДокументация |
| Node.js 11.15.0 | 2019-04-30 | 7.0.276.38 | 6.7.0 | 67 | ReleasesСписок измененийДокументация | |
| Node.js 10.24.1 | Dubnium | 2021-04-06 | 6.8.275.32 | 6.14.12 | 64 | ReleasesСписок измененийДокументация |
| Node.js 9.11.2 | 2018-06-12 | 6.2.414.46 | 5.6.0 | 59 | ReleasesСписок измененийДокументация | |
| Node.js 8.17.0 | Carbon | 2019-12-17 | 6.2.414.78 | 6.13.4 | 57 | ReleasesСписок измененийДокументация |
| Node.js 7.10.1 | 2017-07-11 | 5.5.372.43 | 4.2.0 | 51 | ReleasesСписок измененийДокументация | |
| Node.js 6.17.1 | Boron | 2019-04-03 | 5.1.281.111 | 3.10.10 | 48 | ReleasesСписок измененийДокументация |
| Node.js 5.12.0 | 2016-06-23 | 4.6.85.32 | 3.8.6 | 47 | ReleasesСписок измененийДокументация | |
| Node.js 4.9.1 | Argon | 2018-03-29 | 4.5.103.53 | 2.15.11 | 46 | ReleasesСписок измененийДокументация |
| Node.js 0.12.18 | 2017-02-22 | 3.28.71.20 | 2.15.11 | 14 | ReleasesСписок измененийДокументация |
[1]: NODE_MODULE_VERSION относится к номеру версии Node.js ABI (двоичный интерфейс приложения), который используется для определения того, в какие версии скомпилированных двоичных файлов C++ Node.js можно загружать файлы без необходимости перекомпиляции. Раньше он хранился как шестнадцатеричное значение в более ранних версиях, но теперь представляется как целое число.
Copyright OpenJS Foundation and Node.js contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
Node.js (64-bit)
As an asynchronous event-driven JavaScript runtime, Node is designed to build scalable network applications. In the following «hello world» example, many connections can be handled concurrently. Upon each connection, the callback is fired, but if there is no work to be done, Node 64 bit will sleep.
This is in contrast to today’s more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Furthermore, users of Nodejs are free from worries of dead-locking the process, since there are no locks. Almost no function in the app directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.
Node.js is similar in design to and influenced by, systems like Ruby’s Event Machine or Python‘s Twisted. It takes the event model a bit further. It presents an event loop as a runtime construct instead of a library. In other systems, there is always a blocking call to start the event-loop. Typically behavior is defined through callbacks at the beginning of a script and at the end starts a server through a blocking call like EventMachine::run(). In Node js, there is no such start-the-event-loop call. It simply enters the event loop after executing the input script. The tool exits the event loop when there are no more callbacks to perform. This behavior is like browser JavaScript — the event loop is hidden from the user.
HTTP is a first-class citizen in Nodejs, designed with streaming and low latency in mind. This makes Node js well suited for the foundation of a web library or framework.
Just because Nodejs is designed without threads, doesn’t mean you cannot take advantage of multiple cores in your environment. Child processes can be spawned by using child_process.fork() API, and are designed to be easy to communicate with. Built upon that same interface is the cluster module, which allows you to share sockets between processes to enable load balancing over your cores.
Also Available: Node.js (32-bit) and Node.js for Mac
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
broofa / node-int64 Public archive
Support for representing 64-bit integers in JavaScript
License
broofa/node-int64
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
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, it looks like BigInts will soon be a formally accepted feature, obsoleting the need for this package.
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 if you’re interested. Otherwise I’ll be npm-deprecating this at some future date.
JavaScript Numbers are represented as IEEE 754 double-precision floats. Unfortunately, this means they lose integer precision for values beyond +/- 2^^53. For projects that need to accurately handle 64-bit ints, such as node-thrift, a performant, Number-like class is needed. Int64 is that class.
Int64 instances look and feel much like JS-native Numbers. By way of example .
// First, let's illustrate the problem . > (0x123456789).toString(16) '123456789' // > (0x123456789abcdef0).toString(16) '123456789abcdf00' // // So let's create a couple Int64s using the above values . // Require, of course > Int64 = require('node-int64') // x's value is what we expect (the decimal value of 0x123456789) > x = new Int64(0x123456789) [Int64 value:4886718345 octets:00 00 00 01 23 45 67 89] // y's value is Infinity because it's outside the range of integer // precision. But that's okay - it's still useful because it's internal // representation (octets) is what we passed in > y = new Int64('123456789abcdef0') [Int64 value:Infinity octets:12 34 56 78 9a bc de f0] // Let's do some math. Int64's behave like Numbers. (Sorry, Int64 isn't // for doing 64-bit integer arithmetic (yet) - it's just for carrying // around int64 values > x + 1 4886718346 > y + 1 Infinity // Int64 string operations . > 'value: ' + x 'value: 4886718345' > 'value: ' + y 'value: Infinity' > x.toString(2) '100100011010001010110011110001001' > y.toString(2) 'Infinity' // Use JS's isFinite() method to see if the Int64 value is in the // integer-precise range of JS values > isFinite(x) true > isFinite(y) false // Get an octet string representation. (Yay, y is what we put in!) > x.toOctetString() '0000000123456789' > y.toOctetString() '123456789abcdef0' // Finally, some other ways to create Int64s . // Pass hi/lo words > new Int64(0x12345678, 0x9abcdef0) [Int64 value:Infinity octets:12 34 56 78 9a bc de f0] // Pass a Buffer > new Int64(new Buffer([0x12, 0x34, 0x56, 0x78, 0x9a, 0xbc, 0xde, 0xf0])) [Int64 value:Infinity octets:12 34 56 78 9a bc de f0] // Pass a Buffer and offset > new Int64(new Buffer([0,0,0,0,0x12, 0x34, 0x56, 0x78, 0x9a, 0xbc, 0xde, 0xf0]), 4) [Int64 value:Infinity octets:12 34 56 78 9a bc de f0] // Pull out into a buffer > new Int64(new Buffer([0x12, 0x34, 0x56, 0x78, 0x9a, 0xbc, 0xde, 0xf0])).toBuffer() Buffer 12 34 56 78 9a bc de f0> // Or copy into an existing one (at an offset) > var buf = new Buffer(1024); > new Int64(new Buffer([0x12, 0x34, 0x56, 0x78, 0x9a, 0xbc, 0xde, 0xf0])).copy(buf, 512);
About
Support for representing 64-bit integers in JavaScript
Previous Releases
Releases 1.x through 3.x were called «io.js» as they were part of the io.js fork. As of Node.js 4.0.0 the former release lines of io.js converged with Node.js 0.12.x into unified Node.js releases.
Looking for latest release of a version branch?
| Version | LTS | Date | V8 | npm | NODE_MODULE_VERSION[1] | |
| Node.js 20.4.0 | 2023-07-04 | 11.3.244.8 | 9.7.2 | 115 | ReleasesChangelogDocs | |
| Node.js 19.9.0 | 2023-04-10 | 10.8.168.25 | 9.6.3 | 111 | ReleasesChangelogDocs | |
| Node.js 18.17.0 | Hydrogen | 2023-07-18 | 10.2.154.26 | 9.6.7 | 108 | ReleasesChangelogDocs |
| Node.js 17.9.1 | 2022-06-01 | 9.6.180.15 | 8.11.0 | 102 | ReleasesChangelogDocs | |
| Node.js 16.20.1 | Gallium | 2023-06-20 | 9.4.146.26 | 8.19.4 | 93 | ReleasesChangelogDocs |
| Node.js 15.14.0 | 2021-04-06 | 8.6.395.17 | 7.7.6 | 88 | ReleasesChangelogDocs | |
| Node.js 14.21.3 | Fermium | 2023-02-16 | 8.4.371.23 | 6.14.18 | 83 | ReleasesChangelogDocs |
| Node.js 13.14.0 | 2020-04-29 | 7.9.317.25 | 6.14.4 | 79 | ReleasesChangelogDocs | |
| Node.js 12.22.12 | Erbium | 2022-04-05 | 7.8.279.23 | 6.14.16 | 72 | ReleasesChangelogDocs |
| Node.js 11.15.0 | 2019-04-30 | 7.0.276.38 | 6.7.0 | 67 | ReleasesChangelogDocs | |
| Node.js 10.24.1 | Dubnium | 2021-04-06 | 6.8.275.32 | 6.14.12 | 64 | ReleasesChangelogDocs |
| Node.js 9.11.2 | 2018-06-12 | 6.2.414.46 | 5.6.0 | 59 | ReleasesChangelogDocs | |
| Node.js 8.17.0 | Carbon | 2019-12-17 | 6.2.414.78 | 6.13.4 | 57 | ReleasesChangelogDocs |
| Node.js 7.10.1 | 2017-07-11 | 5.5.372.43 | 4.2.0 | 51 | ReleasesChangelogDocs | |
| Node.js 6.17.1 | Boron | 2019-04-03 | 5.1.281.111 | 3.10.10 | 48 | ReleasesChangelogDocs |
| Node.js 5.12.0 | 2016-06-23 | 4.6.85.32 | 3.8.6 | 47 | ReleasesChangelogDocs | |
| Node.js 4.9.1 | Argon | 2018-03-29 | 4.5.103.53 | 2.15.11 | 46 | ReleasesChangelogDocs |
| Node.js 0.12.18 | 2017-02-22 | 3.28.71.20 | 2.15.11 | 14 | ReleasesChangelogDocs |
[1]: NODE_MODULE_VERSION refers to the ABI (application binary interface) version number of Node.js, used to determine which versions of Node.js compiled C++ add-on binaries can be loaded in to without needing to be re-compiled. It used to be stored as hex value in earlier versions, but is now represented as an integer.
Copyright OpenJS Foundation and Node.js contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.