Leonidas

The issue was introduced by the babel plugin transform react jsx source in v7.9.0 Since newer plugin versions dont support retrieving a column number anmyore, 0 should be used as...

Same additional info: The problem seems to lie in the server side mutation / query superJSON stringifying. In legacy blitzJS, when such a custom error was thrown the API endpoint...

@siddhsuresh Hello, i have some follow up info - which indicates that it seems to be an issue of the rpc resolver Using [email protected] (the same version used in @blitzjs/rpc...

> Thanks for the detailed update. I will take another look soon. Hello @siddhsuresh I have found a solution for this problem. I think the custom logger tslog is responsible...

Weird! If have just today forked the playground demo where i use a string array (just like committed here) - in order to clear both marks for subscript and subscript...

> just stumbled to this issue myself – the correct form to use is the last one: > > ```ts > const message = t(i18n)`${plural(count, { > one: `${name} has...

The error message says that the prescribed node js version of 16 is incompatible with vercel build, which wants to have v18.

Since node v16 isnt supported by vercel anymore i bumped the node version to v22 (current long term support version). I added the node option for legacy openssl support via...