Failure to deploy client with Wasp CLI
I'm trying to deploy my app via the Wasp CLI (
wasp deploy fly launch my-wasp-app mia), but the client always fails (see attached image). Only the server and db deploy successfully to Fly.io.
It looks like someone made a PR with the same issue: https://github.com/wasp-lang/open-saas/issues/77...
Using Cypress for end to end testing and getting a 401 error, not to sure why
I created a cypress test using cy.visit('http://localhost:3000') and im getting a 401 error. I used a sample test provided by the docs and that works
After migration flowbite-react is not working
I migrated from version 0.11 to 0.12. Following the steps, I managed to fix everything except for flowbite-react. I'm not sure if the issue lies with the library or my migration process, so I'll explain the whole process. First, I added Tailwind CSS by creating
tailwind.config.cjs and postcss.config.cjs files. After that, I imported Tailwind CSS into the CSS file and enabled Tailwind to work.
Following the documentation for installing dependencies, I installed flowbite-react with the command npm install -D flowbite-react. Then, I added the flowbite plugin to tailwind.config.cjs so it looks like this:
```javascript...
import actions into main.wasp
I am struggling with the following problem:
I defined an action in the actions.ts but I get the message that it is not exported.
In the Browser I get the message that the import of actions.js failed....
Tried to run open-saas on my Mac Mini M1, here are my thoughts:
So, a few weeks ago I discovered wasp via Mage and loved the idea behind it, and have been trying to make it work properly since then. Recently got invited to test again via a dev.to post and here I am, adding some comments:
- 0.12 is a huge improvement, even after installing nvm I still had problems running wasp. Now at least the first steps are running 😛
- I tried open saas using /wasp new/, install was a bliss, but the steps to run it should be more clear. On medium and dev.to it seems that it's just a matter of executing /wasp start db/ and after executing it I got an error talking about docker not installed. I had to go all the way to the documentation and see how to "fix" it (I'm using quotes as it's not a bug per se, more a nuisance, more later);
- OK, docker running locally, postgress installed, IT'S ALIVE! But... the sign up asks for "user" and "password" and later, when I try to buy something, nothing happens. Just after checking the logs I saw the error saying that I need to have an email o_O...
