Salem

Got it. I'll hold off on reviewing this until I hear more, just so I can prioritize clearing out some of the outstanding backlog.

Thank you @elliotpeele! I'm a little swamped at the moment, but I haven't forgotten about this PR. I appreciate the update and will give it a closer look shortly.

hey @kkom, I'm going to try and set aside some time to day to validate this PR. Thanks again (to everyone on this PR) for being patient.

Seconded, and it could be cool to see a list of things that would be turned into features. One thought is that it could be interesting to include it as...

Sorry for the late reply here! This sounds super reasonable and we would be totally down to accept a PR for this.

Hey, I'm glad you're interested in Kevin! I have a bunch of questions. 1. Can you tell me a bit more about what your webpack config looks like? 2. What...

Hey! I've run into the same error as you did initially (`Error accessing result set, column not found: datetime_precision`) when trying to do my very first `prisma db pull` on...

I ran into the same problem on my end. ```ts @Entity("vendor") export class VendorEntity implements S_Vendor { @PrimaryColumn() id!: string; @OneToMany(() => MeterEntity, (meter) => meter.vendor) meters!: Promise; } export...

I had the same problem as above (the `MESSAGEPORT` one) with essentially the same stack trace. I thought it must have something to do with the `node-domexception` polyfill that `node-fetch`...

@inglor it is being considered. Alas, there are only a few of us, and we all have full-time jobs and have had a rocky few years. Thanks for being patient...