The latest articles on DEV Community by MD Tarekul Islam Sabbir (@tisabbir). https://dev.to/tisabbir https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2968823%2F5407dad7-06e3-4086-84aa-e263f9d60143.png https://dev.to/tisabbir en MD Tarekul Islam Sabbir Fri, 28 Mar 2025 06:57:28 +0000 https://dev.to/tisabbir/how-i-fixed-my-broken-signup-flow-and-what-it-taught-me-4140 https://dev.to/tisabbir/how-i-fixed-my-broken-signup-flow-and-what-it-taught-me-4140 <p>You know that moment when your code <em>should</em> work, but it's silently failing? Yeah, that was me last week. I built a user signup API, and it kept throwing vague errors like <em>"Something went wrong"</em> with no details. Super helpful, right?</p> <h2> The Breaking Point </h2> <p>I finally saw this in my logs:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>TypeError: Cannot read properties of undefined (reading 'collection') </code></pre> </div> <p>Turns out, my database connection wasn't actually <em>connecting</em>. I'd forgotten the critical <code>await client.connect()</code>—oops. My <code>connectDB()</code> function was basically a fancy no-op.</p> <h2> What Went Wrong </h2> <ol> <li> <p><strong>Ghost Errors</strong></p> <ul> <li>My <code>try/catch</code> swallowed errors instead of passing them up</li> <li>Result: Empty <code>error: {}</code> responses. <em>Cool. Very descriptive.</em> </li> </ul> </li> <li> <p><strong>HTTP Codes Gone Wild</strong></p> <ul> <li>I used <code>304 Not Modified</code> for existing users (🤦‍♂️)</li> <li>Reality check: <code>304</code> is for caching. <code>409 Conflict</code> is the correct "user exists" code</li> </ul> </li> <li> <p><strong>Security? What Security?</strong></p> <ul> <li>Passwords were flying in plaintext</li> <li>Zero input validation. <em>"What's an injection attack?"</em> – Me, before Google</li> </ul> </li> </ol> <h2> How I Fixed It </h2> <ol> <li> <p><strong>Database Connection Bootcamp</strong></p> <ul> <li>Added <code>await client.connect()</code>. <em>Shocking, I know.</em> </li> <li>Cached the connection so it doesn't re-connect every request</li> </ul> </li> <li> <p><strong>Error Handling That Doesn't Suck</strong></p> <ul> <li>Started logging errors with <code>console.error</code> </li> <li>Returned actual error messages instead of <code>{}</code> </li> </ul> </li> <li> <p><strong>HTTP Codes That Make Sense</strong></p> <ul> <li> <code>201 Created</code> for new users</li> <li> <code>409 Conflict</code> for duplicates</li> <li> <code>500</code> only for <em>real</em> server meltdowns</li> </ul> </li> <li> <p><strong>Basic Security Hygiene</strong></p> <ul> <li>Added <code>bcrypt</code> for password hashing</li> <li>Validated emails (no more <code>"not_an_email"</code> signups)</li> </ul> </li> </ol> <h2> Lessons Learned </h2> <ul> <li> <strong>Debugging 101:</strong> Isolate the damn issue. Test DB connections separately</li> <li> <strong>HTTP Codes Matter:</strong> A wrong status code confuses everyone (including future you)</li> <li> <strong>Never Trust User Input:</strong> Validate early, hash passwords, and sanitize everything</li> </ul> <p><strong>Moral of the Story?</strong><br> If your code fails silently, you're in for a bad time. Log errors, use proper status codes, and <em>always</em> secure user data. Now my signup flow actually works—and doesn't embarrass me. 🎉</p> <p><em>— MD Tarekul Islam Sabbir, slightly wiser than last week</em></p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fh9w0eyj7k2cxwiuxfs8q.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fh9w0eyj7k2cxwiuxfs8q.png" alt="User Signup Flow Diagram" width="800" height="1506"></a></p> webdev programming learning nextjs