Eemeli Aro

Does that mean that you're effectively treating 100% fuzzy matches as non-fuzzy?

I ended up thinking about this in the context of #425 and #427, by wondering whether we ought to have a shorthand like `:integer` baked in as a default formatter...

> > 1. Could you clarify what's the use case of pretty-printed JSON output? For single-shot manual use, wouldn't the same be served by piping the output to a separate...

Here's the full set of methods/accessors that the proposed [JS implementation](https://github.com/tc39/proposal-intl-messageformat#messagevalue) uses: - get options - get value - format to string - format to parts - select keys As...

> Specifically, while a function may eagerly format its operand to a string, it should (must?) also return the raw underlying value and the formatting options used for formatting, in...

> We have subsystems on node.js, in which using of the `require` is prohibited due to ISEC policies (to avoid manipulation of module contents). Could you provide some links explaining...

The increase in security is wholly illusory. Consider the following, for instance: ```js // patch.mjs import { Document } from 'yaml' Document.prototype.toJS = () => 'foo' ``` ```js // index.mjs...

> Well, immutable references in the module cache are just the first step, but more are needed. warmup + deep Object.freeze might fit your snippet. Given that I'm not willing...

> Reasonable. But module refs obtained via `require` and `import` are alway different, afair: > > ```js > var y1 = require('yaml'), y2 = await import('yaml'); console.log(y1 === y2) >...

Ah, I'd missed that you'd changed your proposal to defining `yaml/esm` and, presumably, `yaml/esm/util`. That would indeed avoid making this a breaking change, but I'm still not at all convinced...