Maciek Sakrejda

Yeah, that's exactly what I had in mind (N.B.: I know almost nothing about Avro or bottledwater =D ). The memory usage is certainly a concern, too, but that'd be...

It's been a while so maybe not a lot of interest in adding this, but for what it's worth, I would also find this useful, especially when the approvals are...

I misunderstood the original request--I did not realize per-package `why` is present in the markdown report. I need the CSV report, and, if anyone is interested, I started a branch...

@xtreme-shane-lattanzio by "fall back" I meant "display the `--why` of the permitted license if the package was not manually approved". Right now my branch does not do that--it only displays...

@xtreme-shane-lattanzio I was vaguely thinking of something like the `--why` of the oldest permitted license for the package, or perhaps the concatenated `--why`s of all licenses, prefixed with the license...

Digging into this a bit, I found that the problem was probably an outdated `@babel/core`. I updated it and then started getting an error similar to https://github.com/storybookjs/storybook/issues/12893, but I followed...

My project also uses index imports. Sapling seems very cool, but I can't really use it due to this. Is this something you would accept a contribution for @PLCoster ?...

Also, any chance pgtyped could support .env files? Right now it's hard to use `dotenv` for this with pgtyped, since pgtyped is its own CLI. Loading a .env file with...

@tbo oh that's great, thanks! I looked at using `dotenv`, but I missed you can use it like a wrapper like `env`. I'd still love to have pgtyped fall back...

Thanks for clarifying that @charmander -- I came here with the same concern as @claytongulick and found this issue, but what you're saying makes sense.