Gregory Markou

@Berkmann18 I found a weird behaviour. If you have renamed your repo, and have not updated the remote on your project locally it won't allow it to work.

We're trying to get our TypeScript rewrite finished (we're just about there) and thus have put a feature freeze on 1.x until it's done.

I've made a few changes and revisions since early August, and I think we're add the "test it and break it" phase. For the updated spec you can find it...

Any chance this might get implemented. I've been chatting with a lot of folks lately who would still find this useful

@TwitchBronBron did you ever solve this?

It seems that node-gyp is plaguing the install phase (node 16) and for whatever reason my m1 doesn't allow me to use anything less then node 16

I have not. I only ran with npm

I'm having this issue as well... Does anyone have a temporary fix? How can I override the define_current_entity_getter method?

hiiiii @rekmarks

any news on this/?