You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running through the flow with the "Deploy to Netlify" button on a Windows computer in WSL and after getting the Supabase environment variable setup I ran into a tailwind error running it locally. I was streaming on Twitch, so here is the timestamp where it happened and here are the changes I made to fix it. I did also install prisma, prisma client, and ts-node on this commit as well.
It was complaining that it could not resolve this import import tailwindStylesheetUrl from "./styles/tailwind.css";. But, as you can see in the video it was there.
I tried running another site I had setup the same way on a Macbook today and did not run into the same issues. From what I saw in the error everything appeared to be correctly linked, so I'm not sure if this is an issue that even needs to be resolved, but I wanted to bring it to your attention in case anyone else experiences it.
The text was updated successfully, but these errors were encountered:
Thank you for reporting this @brittneypostma! I'll take a gander at it on Monday. I suspect it has something to do with the development scripts in particular since you didn't have this issue on the deployed experience right?
I was running through the flow with the "Deploy to Netlify" button on a Windows computer in WSL and after getting the Supabase environment variable setup I ran into a tailwind error running it locally. I was streaming on Twitch, so here is the timestamp where it happened and here are the changes I made to fix it. I did also install prisma, prisma client, and ts-node on this commit as well.
It was complaining that it could not resolve this import
import tailwindStylesheetUrl from "./styles/tailwind.css";
. But, as you can see in the video it was there.I tried running another site I had setup the same way on a Macbook today and did not run into the same issues. From what I saw in the error everything appeared to be correctly linked, so I'm not sure if this is an issue that even needs to be resolved, but I wanted to bring it to your attention in case anyone else experiences it.
The text was updated successfully, but these errors were encountered: