Maybe that's the real bug of Day 15 we are supposed to find :D
Maybe that's the real bug of Day 15 we are supposed to find :D
@tkdodo.eu i have noticed an issue with the Day 15 Bug. I can "fix" the bug and resolve the issue by just renaming the log function im supposed to fix. This can't be right? Atleast the explanation at the end, hints at a different solution ^^
Shitty button components. We've all seen them, we've all written them. But they don't have to stay shitty! I wrote about building better button components, with simple patterns that I now use everywhere.
Also: the word "button" appears 181 times in it.
timomeh.de/posts/a-bett...
yikes
i have always wondered, what color scheme do you use?
i imported a GitHub repository on their site. there is an option where you can change the framwork that was detected. use vite with the template lee and i linked
also immediately looked for a announcement post from vercel or lee, but couldn't finde anything so it guess it's not finished yet
freaked me out two days ago, because I took down the deployment and wanted to re-deploy. saw it detected react-router as a framework and thought nice, but it ended up not working. after i switched back to vite, it worked fine
with this template you have to select `vite` as a envrioment(?) in the vercel deploy screen. otherwise it won't work
github.com/remix-run/re...
did you use the template? deploying the template works just fine. i used the template @leerob.com posted and copied my code into it. worked fine for me. I also saw the new auto-detection works for react-router. altough i have not tried to deploy a new react-router app just yet
never mind, found the issue! :)
As always the person that sits in front of the machine is the biggest issue
hey @leerob.com, unfortunately I can't seem to find the error. I checked quite a lot, env variables are correctly set. build runs locally, everything just works.
One thing, i wanted to check are api routes like `api.auth.$.ts`. this is one of the first routes that get hit because of my route guard
anyways, thanks for the help @leerob.com
I'm going to investigate if I can see a more detailed error log of the issue or maybe build the application step by step and see when the error occures
Thanks for the unbelievable quick reply, however, i'm running into a new error (kinda good i guess?). the 404 error message is gone but all i see now is a "Internal Server Error" Message.
Do I need to adjust anything in the Build & Development Settings?
further more, i have some overwrites
Hey @leerob.com ๐, I'm having issues deploying my react-router v7 app to vercel and could really need your help.
I already tried this, but it does not work :(
```
{
"builds": [{ "src": "./index.js", "use": "@vercel/node" }],
"routes": [{ "src": "/[^.]+", "dest": "/", "status": 200 }]
}
```
"AT proto"?
:(
wouldnt this be the product owner most of the time?
should be maintained by only a couple of people since the reactions could be an easy target to trolls and thus worsen the quality of the answers
most of the stuff I saw was labeled as layouts. Also in the very basic start example they were only used to create a layout which I find missleading since they can be used for stuff like this.