Aaron Huggins

This is resolved at https://github.com/aaronhuggins/cbor-redux.

For interested parties, [here's how the docs are shaping up](https://doc.deno.land/https://deno.land/x/[email protected]/mod.ts). Though the docs will be generated via doc.deno.land, they are applicable to Node/Deno/Web since it's literally all the same code.

@letmaik I've read the spec, given this a ton of thought, and I feel that overwriting is an appropriate handle per spec. It seems to leave room for implementation-specific parsing...

I believe from a language perspective that the first *must not* is satisfied by the encode process. The second *must not* I am interpreting as "don't present more than one...

I'm in favor of the following, with proper documentation: 1. Add a configuration API with `mode: 'loose'|'strict'`, where loose is the default 2. Loose would be the current behavior, nothing...

Yuck, you're right, module-wide options wouldn't work well in this context *at all*. What do you think of putting all the options in an options bag to be passed to...

Yeah, I'm going to drop `observe` altogether and add `reviver` to the decode API and `replacer` to the encode API. I have a use case for that functionality, and it...

@letmaik Hey, may I pick your brain a little bit more? What do you think of the docs here? https://doc.deno.land/https://raw.githubusercontent.com/aaronhuggins/cbor-redux/0c8b3f4fa619fee986dd91e254d999fc9cfd396e/mod.ts That document should be largely applicable to Node/Deno/Web. Would be...

I'll be cuing this up this month. My plan is to move wholly over to Deno-only support *in the repo* and then deploy Node-compatible version to NPM using https://github.com/denoland/dnt.

This is a really good feedback. I haven't run into this usecase for my personal projects, but I've seen this in the wild and it's pretty darn common to need...