During a recent project, I encountered a strange issue while deploying a Sitecore XM Cloud solution to a new Netlify environment. The problem was related to Deno installation, which unexpectedly disrupted the deployment process. If you've run into a similar issue—or you're just curious about what Deno is and how it ties into Netlify—keep reading. I’ll walk you through what happened, explain what Deno is, and show you how to resolve the issue.
While working on a recent Sitecore XM Cloud project, I ran into a frustrating issue when trying to build my Next.js app locally using pnpm run build. No matter what I tried, the build kept failing with a 60-second timeout. The error message always began with:
⚠ Sending SIGTERM signal to Next.js build worker due to timeout of 60 seconds. Subsequent errors may be a result of the worker exiting.
If you’ve encountered this error and are stuck like I was — don’t worry. In this post, I’ll walk you through what’s causing it and how to fix it.
Recently, I was asked to conduct an audit for a Sitecore headless website built using Sitecore JSS and Next.js. As part of this process, I reviewed various aspects of the solution—from content modeling and rendering strategies to performance, deployment, and developer experience. In this blog post—and in upcoming entries—I’ll be sharing some of the critical areas you should evaluate, along with best practices to follow when auditing or building a Sitecore JSS/Next.js application. Whether you're a Sitecore developer, architect, or technical lead, these insights can help ensure your implementation is scalable, maintainable, and optimized for a modern digital experience.
Curious to learn more? Keep reading!
