Martin Zagora

That indeed worked: https://github.com/pureprofile-warp/babel-preset-pp-node4/commit/d6c0d193157d92a49a6296506aab05231cfbcb6b Thanks @kt3k

Hey, if you open a pull request I'm happy to have a look and merge it if it doesn't break anything.

@peteorpeter happy to merge a PR. Third parameter is this: https://github.com/zaggino/z-schema/blob/master/index.d.ts#L7-L29 so: ``` validate(json: any, schema: any, options: Validator.Options): boolean ``` schemaPath is missing from Validator.Options

benchmark is currently failing, if someone can submit a PR fixing it, i'm happy to refresh the tests ... to run them do just: ``` npm install node benchmark.js ```...

Why instead of using format lookup under county you don't put it directly on object and check that like this? It makes more sense to put format there since it...

Can you submit a test-case for the issue?

3.0 was a complete rewrite because 2.0 used a lot of promises which made it slow, compare you current usage with the one in the docs speed benchmarks comparing v2...

👍 agree with you, if you'll open a PR with tests passing i'll merge it

hi, `ZSchema-browser` is already browserified file, maybe try just using `import * as ZSchema from 'z-schema'` when using roll-up ?

Well, the errors should already point to place where the validation failed, so the API should be possible. You probably would need to propose an API, sample inputs/outputs and then...