Matt Bishop

This is actually correct behaviour because 1.1 is a double-precision float value, which is 64 bits. You can see in the Node REPL: ``` > Math.fround(1.1) 1.100000023841858 ```

Interesting, but why would you want to replace a step? I like the rigidity of the steps as they are now.

```typescript import {pipeline} from "stream/promises" const sonicBoom = new SonicBoom({dest:`${outDir}/base_amounts.xml`}) await pipeline(aReadStream, transform1, transform2, sonicBoom); ``` ``` TSError: ⨯ Unable to compile TypeScript: src/index.ts:14:9 - error TS2769: No overload matches...

This works on Node 16, so it might be a @types/node issue: ```js const { pipeline, Readable } = require("node:stream") const SonicBoom = require("sonic-boom") // works Readable.from("Hello pipe()!") .pipe(new SonicBoom({dest:...

I think I'll try creating a `SonicBoomWritableStream` first and see how it looks. I don't think I will make much progress on the node front!

It looks less-disruptive to expand SonicBoom and add the WritableStream methods instead of making a separate class. Any objections?

Hello, any luck getting a fix in?

I love the idea of BigInt better than Long. 👍 As for float, it may not be obvious what type of float should be used. My approach was to just...