-
Since wasp doesn't have a long running node process on the backend in dev (like i.e. next.js) the main server app talks to is killed and restarted all the time -> causing our frontend to not be able t…
-
I realize this is a non-issue compared to the decentralization problem, but this might be a good base to work with for the marketplace/frontend itself:
https://github.com/Bit-Wasp/BitWasp
-
We require a certain Node.js version to be available when running `wasp start`, it would be nice for users to have a `.nvmrc` file available in the project dir.
This would enable users to execute …
-
-
Inspired by this Discord convo https://discord.com/channels/686873244791210014/1229992558503923805/1229992558503923805, and this is not the first time this has been brought up.
We should have a pag…
-
Since open saas has quite picked up in the usage, I was wondering if it would make sense to consider some kind of versioning scheme.
In the sense of that we have something like open-saas 1.0.0, 1.2…
-
Right now, errors are coming directly from client/server, and often it is not easy to connect them with the Wasp source code, since generated code should be opaque to the user, but in this sense it is…
-
Two users reported this week that they were getting memory errors loading the latest CI build a2e3522 that I provided them. Neither did anything special like taking apps in and out of RAM.
Here is…
-
Ideas:
- Type safe routes (https://tanstack.com/router/v1/docs/guide/type-safety)
- a `Link` component (maybe we already have this?)
- nested routes
- layouts
sodic updated
2 months ago
-
Update Plotfit docs to remove xxx
State the manual ordering takes ordering from Wasp and Host names order
Make sure parrallel option of resampling is more robust