The latest articles on DEV Community by Lucky Singh (@lucky_singh_0dd24b31467d9). https://dev.to/lucky_singh_0dd24b31467d9 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%2F3764821%2F81ba2cf9-da4e-4e4c-94a9-aac602d00383.jpg https://dev.to/lucky_singh_0dd24b31467d9 en Lucky Singh Tue, 10 Feb 2026 17:58:57 +0000 https://dev.to/lucky_singh_0dd24b31467d9/fixing-a-critical-json-bug-that-broke-an-entire-nextjs-website-3053 https://dev.to/lucky_singh_0dd24b31467d9/fixing-a-critical-json-bug-that-broke-an-entire-nextjs-website-3053 <p>While contributing to the AsyncAPI website, I encountered a critical issue that completely broke the production build. The entire website failed to load due to a small but impactful mistake in a JSON configuration file.</p> <p>The problem was located in config/3.0.0.json, where an inline comment had been added inside the JSON object. Unlike JavaScript, JSON does not support comments. This caused a JSON parsing failure, which in turn triggered a Next.js build error and displayed an error overlay across all pages of the website.</p> <p>To diagnose the issue, I closely examined the error message and traced it back to the exact line causing the failure. Once identified, the fix was straightforward: remove the unsupported comment and restore valid JSON syntax. After applying this change, the website compiled successfully and loaded without any errors.</p> <p>This experience reinforced an important lesson for me: small syntax mistakes in configuration files can have site-wide consequences, especially in production systems. It also highlighted the importance of understanding format specifications and validating configuration changes carefully.</p> <p>Through this contribution, I gained hands-on experience debugging a real-world issue, working with build systems, and contributing to the stability of an open-source project. It was a reminder that meaningful open-source contributions aren’t always about adding new features—sometimes they’re about preventing failures and improving reliability.</p> webdev ai Lucky Singh Tue, 10 Feb 2026 17:58:57 +0000 https://dev.to/lucky_singh_0dd24b31467d9/fixing-a-critical-json-bug-that-broke-an-entire-nextjs-website-5b66 https://dev.to/lucky_singh_0dd24b31467d9/fixing-a-critical-json-bug-that-broke-an-entire-nextjs-website-5b66 <p>While contributing to the AsyncAPI website, I encountered a critical issue that completely broke the production build. The entire website failed to load due to a small but impactful mistake in a JSON configuration file.</p> <p>The problem was located in config/3.0.0.json, where an inline comment had been added inside the JSON object. Unlike JavaScript, JSON does not support comments. This caused a JSON parsing failure, which in turn triggered a Next.js build error and displayed an error overlay across all pages of the website.</p> <p>To diagnose the issue, I closely examined the error message and traced it back to the exact line causing the failure. Once identified, the fix was straightforward: remove the unsupported comment and restore valid JSON syntax. After applying this change, the website compiled successfully and loaded without any errors.</p> <p>This experience reinforced an important lesson for me: small syntax mistakes in configuration files can have site-wide consequences, especially in production systems. It also highlighted the importance of understanding format specifications and validating configuration changes carefully.</p> <p>Through this contribution, I gained hands-on experience debugging a real-world issue, working with build systems, and contributing to the stability of an open-source project. It was a reminder that meaningful open-source contributions aren’t always about adding new features—sometimes they’re about preventing failures and improving reliability.</p> webdev ai