Closed epoberezkin closed 8 years ago
Ooh, good catch. Fixed in f48ff35 ~= v1.1.2. (Please reopen if your use case is not recursing properly?)
Also brings up an interesting idea of maybe changing the Levenshtein algorithm cost based on whether a small part has changed vs. the whole entry, but that's probably incurs more complexity than it's worth.
Err, make that v1.1.3 (I forgot I had {..., main: './rfc6902.js'}
in my package.json
and versioned/built in the wrong order).
Thanks!
instead of removing a single property