
Research Before VibeCoding: Libraries and Frameworks
Today, I was cleaning up a vibe-coded project in NextJS, with a custom hook for validating and handling Form Submission, i.e., useForm . Form works? Yes, but only for small forms. Is it maintainable? Might be. Is it scalable? No. For complex forms, it was giving an error related to rendering, I failed to fix the issue I tried for an hour to untangle the spaghetti, but failed. Used AI tools, but was unable to fix it. Moreover, AI even hallucinated that it solved the issue. The Last Resort As a last resort, I have 2 choices: either to recreate the custom hook from scratch, or use well known library such as Formik and Yup . I chose to go with libraries. Why? I don't want to reinvent the wheel, solving every known edge case/corner case, and testing the forms in major browsers. These libraries are well maintained from years. Clear and easy to read documentation. Easy to upgrade to future ReactJS versions Verdict Before diving into coding, make sure to research whether the feature you're bui
Continue reading on Dev.to React
Opens in a new tab


![[MM’s] Boot Notes — The Day Zero Blueprint — Test Smarter on Day One](/_next/image?url=https%3A%2F%2Fcdn-images-1.medium.com%2Fmax%2F1368%2F1*AvVpFzkFJBm-xns4niPLAA.png&w=1200&q=75)

