Brandon der Blätter

I'm having a similar issue. where `IMyContentTypeName` incorrectly extends interface `Entry`: ``` Types of property 'sys' are incompatible. Type '{ id: string; type: string; createdAt: string; updatedAt: string; locale: string;...

it already says "failed to load extension" for me in Chrome 103

the maintainer left contact info in the README, I reached out on Twitter to see what's up

I'm in contact with the maintainer. since this issue is about fixing vulnerabilities in the dependencies let's focus on that here. over half the open issues look like they mention...

dependencies are now updated and pushed to NPM. @ncb000gt @felipemarts I think this issue can be closed

most likely there's something wrong with the way you deployed it. you sure the original job isn't still running? you sure you didn't run the script twice on AWS? deployment...

@GabrielAnca I believe that would work. if it passes the type check immediately after generation that's pretty much all I need

we're looking at a rewrite of that function yes because this has been an issue for a while. if you have any ideas for a specific approach we're open to...

is the Node process still running when the cron job stops? is it only the cron part that fails?

your computer suspends on a schedule? does it automatically un-suspend? my guess is the `node-cron` function that gets the next time is being confused by your computer's suspension schedule. here's...