Evan

@HoldYourWaffle -- Unfortunately, no. The fork now generates [io-ts types](https://github.com/gcanti/io-ts) instead of regular Typescript interfaces. While the output types _can_ be used just as regular types, this change probably isn't...

I'd also be happy to contribute to a new maintained fork in the future. (@HoldYourWaffle -- your CC PR was a great start to some really helpful things that we've...

@HoldYourWaffle -- Regarding the implementation differences: I think that the main difference is that the camel case options were `columns` and `tables` instead of `columns` and `types` (the fork doesn't...

2. The https://github.com/xiamx/schemats/ fork is mostly url changes (`SweetIQ` -> `xiamx`), build/configuration fixes, and package updates. I think that it definitely makes sense to use that fork as the starting...

In the case that PRs cannot be transferred, what would you anticipate the fallback plan to be? I suppose that any of the larger PRs could be separately forked and...

Perhaps I'm missing something, but couldn't this be achieved by directly calling the desired script from `default`? e.g. ```js module.exports = { build: 'yarn some-build-cmd', dev: 'yarn some-other-cmd', default: 'nps...