-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to ESM #83
base: main
Are you sure you want to change the base?
Move to ESM #83
Conversation
Perhaps we could use Related, what is |
That library has transferred actually (not sure if it's been republished yet). There's definitely more well-known symbols out there but maybe there's a better way to encode them.
I'm not bothered either way. There may also be some APIs we could use, e.g. the structured clone implementation in the
Looks like it's a heuristic for identifying when to treat an object as a list (array). But it could be inlined:
I'd go with 18. 16 is end of life in 9 days. |
Per #82.
Object.hasOwn()
instead ofObject.prototype.hasOwnProperty.call()
xo
(based on configs fromAVA
)well-known-symbols
)lodash
with only the required functions_.flattenDeep
in favor ofArray#flat(Infinity)
A few tests are failing, seems to have to do with serialization and object pointers.