phero
phero copied to clipboard
Full-stack type-safety with pure TypeScript
Running `phero` without internet connection leads to a crash: ``` /Users/kamilafsar/Projects/phero/packages/cli/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53 throw ex; ^ Error: getaddrinfo ENOTFOUND registry.npmjs.org at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) Emitted 'error' event on ClientRequest instance at:...
The loading-animation is not displayed like it should on windows:   Also check if there are more cases like...
We don't enforce a certain version of the `typescript` package, but we do assume 4.8.x for certain things. We should figure out how to best handle this. Should it become...
When working with default values for function parameters, Phero still requires explicit typing to function, which seems like unintended behaviour. 
Would be nice to override the default export path of the phero.generated.ts file
Phero is amazing when using the generated server and client together. But when building a backend which can be consumed by many clients, some of which may not be using...
Inspired by [this comment on YouTube](https://www.youtube.com/watch?v=BS8nRuszlqo&lc=UgwXhvborv6Ip5DeCQF4AaABAg.9hJR98fEVeo9hQ2LgpKSyt), a command to validate if your current `PheroClient` is up to date with a server would be great 👍
I'm not sure this if is something that should be supported, but I'm just dropping it here to atleast start of the discussion. I'm not sure if this is specific...
Trying to import `samen.generated.ts` (either directly or via the created client) within a `.svelte` file result in a runtime error. ``` Uncaught ReferenceError: exports is not defined at ParseResult.js:2:23 at...