How to Build a Fullstack Next.js App (with Storybook & TailwindCSS) 

Glad its helpful, I hope to find time to create more content soon!

@@AlexEagleson We are waiting for more man. You have helped me a lot. Thank you!

Cheers!

literally, i feel like the youtube algorithm surprised me with great content for the first time ever

@@coding7430 Thank you, I'm glad it has helped!

You're welcome!

Glad it's helpful!

Glad it helped!!

@@AlexEagleson sir waiting for more video 🤩

I recently did an interview and used this same setup and it went over really well, hopefully it does for you too!

@@AlexEagleson glad to hear it! thank you! hope it pans out! will be back to update ;)

Thank you! Much appreciated. I think it absolutely could be an option for at least part of it. Getting stories to work in an inheritance-like model could be tricky, but i'd certainly be interested to see any approaches that have tried. Since class components aren't the standard anymore there may be a sensible want to compose new component out of a base component. I'd definitely have to give that some thought

I think I also could probably get better with debugging. The very first thing that I reach for in my toolkit is still a simple console.log, and I find that 95% of that time that helps me identify the issue quickly. For more complex issues I do occasionally reach for the debugger and try to step through the code watching the values of variables change. There are definitely times when I've been able to use that to identify weird behavior I would not have noticed or expected otherwise The last tool I find helpful is the React dev tools for the browser. I use Firefox but i assume they're similar on Chrome. Being able to right click on an element in the DOM inspector and have that mapped to a component which I can see the same and state of is very helpful, particularly when I am working with other people's code. A combination of the above 3 usually gets the job done, but like I said, console.log is still a perfectly valid tool to use for me if it can tell me the answer in seconds and let me move on Another option worth looking at is a launch.json script for VSCode. check out nExt's docs for how they recommend you set it up: nextjs.org/docs/advanced-features/debugging

@@AlexEagleson thanks!

I'd definitely like to! Just a matter of finding the time these days, but that's the intention

I don't believe so (I could be wrong) but even if not, you can add // @ts-check to the top of your storybook config .js files to get type checking from your IDE

Finally got things configured. It seems StoryBook is a little uncooperative if you're using pnpm package manager and not npm or yarn. Using pnpm version 8 or greater and also StoryBook version 7.0.2 or later resolved these issues.

I'm right here! I make videos whenever I have spare time, it's just hard to come by spare time sometimes. Hopefully another one soon :)

please make a video about how create components. for example how use ui frameworks and things like this.

I don't understand how one can say they are building a scalable app with no support for internalization!

Right here!

@@AlexEagleson Good, first of i hope you 're doing well, seconde, why you are not posting next typescript videos anymore or web dev content, third, forget about the last point I have seen your articles so I guess it's okay 👍

@@howuseehim mostly finding time to be honest, recording and editing are very time consuming. I'm working mostly in Rust at the moment and also taking care of a new baby, so extra time is very hard to come by! Thanks for checking in though :)

@@AlexEagleson congratulations 👏