Ben
currently, {} could be caught by `P.object.exact({a: P.any})` pattern.
fixed {} caught by {a:P.any}, but nested object pattern should be tested
during the implementation of this feature, I'm concerned about the following scenarios. 1. nested object, but an exact match for the outer side, and less strict matching inside. (the other...
I think that behavior could easily cause misunderstanding. I thought exact should catch 'exact' object matching, not 'exact matching, but only single depth'. It's a bit ambiguous.
I'll keep implementing with single-depth match version(because it's a sub-spec of full-depth matching), but still not sure it's good design or not.
for now, I just rewrote scripts/build.ts to be run with bun runtime, just for ease. I guess it works just same as the original.
here's the script I use for build ```typescript import { execSync } from "child_process" const globby = require("globby"); import { copyFileSync } from "node:fs" import 'chalk' console.log('Build dist') console.log('yarn clean')...
still looking for some help here😅
Hi. I updated all the contender's versions and tested them on my machine(Macbook Pro M2) and these are the results. ``` "lodash": "4.17.21", "rambda": "9.1.0", "ramda": "0.29.1", "remeda": "1.47.1" node...
maybe the varied result caused by node version. I'll match to yours and check again.