roaring-node

roaring 2.4.0

• CRoaring 4.1.2
• Support for node 22
• Fix memory leak in (x)orMany
• Support new esnext Set methods (union, difference ...)
• Fix typing to support TypeScript 5.6.2

• updated CRoaring to 2.1.2, that has performance improvements and fixes
• Added support for node 21
• Removed support for Node 12 and Node 14 (many dev packages do not support them anymore and they are legacy).

• updated CRoaring to 1.1.5
• Fixes for ranges and at floating point
• Force Ubuntu 20.04 in CI to compile with the right libc version

roaring 2.1.1

• Add the ability to serialize and deserialize a file directly with serializeFileAsync and deserializeFileAsync methods - those two are faster than loading a file in memory and deserialize/serialize in memory and are fully asynchronous. They use mmap if possible.
• Adds the ability to serialize to file text format and deserialize from buffer and from file text formats: newline_separated_values, comma_separated_values, tab_separated_values, json_array
• Adds the ability to serialize and deserialize a binary array of little endian uint32_t values
• Remove COW enabled by default, it could cause issues with asynchronous operations and multi threading - will provide a flag in a new version

• New class RoaringBitmap32ReverseIterator
• Copy On Write (COW) always enabled - this can improve performance and reduce memory usage
• this.reverseIterator(): RoaringBitmap32ReverseIterator
• RoaringBitmap32.of(1, 2, 3 ...)
• this.indexOf(value:number, startIndex?:number): number and this.lastIndexOf(value:number, startIndex?:number)
• this.at(index:number): number
• Array methods: some, reduce, reduceRight, find, findIndex, filter, toSorted, toReversed
• varargs for add, tryAdd, remove, delete
• Update to CRoaring 1.1.2

BREAKING:
map and forEach were not implemented correctly and were not behaving like array.map and array.forEach on the index argument. This is fixed now and index is the index of the item in the set.

roaring 2.0.1

BREAKING: drop support for node 8 and node 10
Add support for node 20
Update CRoaring to version 1.1.2
chore: improved build and CI

• Fix for the aligned buffers
• Update CRoaring to 0.9.8, it contains some important bug fixes

• Fixes #46
• Update roaring to 0.9.6 that contains several important fixes

• Fixes and improves toUint32Array and rangeUint32Array signatures in C++ and typescript
• Update roaring to 0.9.3

• Fixes and improves typescript types: new interface ReadonlyRoaringBitmap32
• new method RoaringBitmap32::asReadonlyView() that returns a readonly view on the given bitmap, all write methods will throw error if called.

• Upgrade to croaring 0.9.2
• Support for frozen serialization and deserialization formats
• New property isFrozen and new method freeze() to make a bitmap readonly
• toUint32ArrayAsync, serializeAsync
• Better APIs with more options for several methods (maxLength and offset, and output as argument for serialize, serializeAsync, toSet, toArray, toUint32Array ...)
• New functions: rangeIntersects, static addOffset
• New functions: bufferAlignedAlloc, bufferAlignedAllocUnsafe, isBufferAligned, ensureBufferAligned
• Proper and precise use of AdjustAmountOfExternalAllocatedMemory for every memory allocation
• Allocation details function getRoaringUsedMemory and static method getInstancesCount to track how much memory is used by roaring bitmaps and how many instances are active

• Update roaring to 0.4.0
• Reduce binary size and loading time by cleaning up and some compiler flags (linux/mac)
• Remove Jest, use Mocha instead
• Compatibility between RoaringBitmap32 and Set, implementation and typescript, so a RoaringBitmap32 can be used as Set.
• Partial mitigation of https://github.com/SalvatorePreviti/roaring-node/issues/37 issue - a call to runOptimize or shrinkToFit will compute the serialized size in bytes of the map and call AdjustAmountOfExternalAllocatedMemory accordingly, call those function when you are finished updating it (or once in a while). Creating a RoaringBitmap32 adds 8192 bytes by default (and removes on destruction).

• Add support for node 14, 15 and 16
• Update Roaring to version 0.3.3
• Add support to roaring_bitmap_range_uint32_array via the new method rangeUint32Array - thanks to @cigolpl
• Use dynamic CPU dispatch of Roaring 0.3.3 instead of having multiple binaries
• Improves compilation time and binary size
• BREAKING CHANGE: now the "portable" flag in all the serialization and deserialization methods is mandatory, functions will throw an error if not passed.

• fixed memory leak with static operations (like RoaringBitmap32.andNot(a, b))
• support for NodeJS 13
• memory management improvements

• Fixes SSE2 detection if supported by CPU but disabled by OS
• Introduces xorMany static function
• Update of CRoaring to v0.2.60

• implementation of rangeCardinality
• optimized removeMany

Support for Node 11