When building my Hubspot CMS React project, it does not work and it returns the following error:
✖ ERROR There were errors building this component:
- An error occurred while building project: xxxx-project.
Error: RPC error from com.hubspot.js.renderer.orchestration.rpc.JsRendererBuildExecutorRpc#invokeBuild->ChirpInternalError[DEADLINE_EXCEEDED]
Hey @aitortomas,
Thanks for posting in the Community!
I’d like to tag in a few Community experts to see what insight they may have! @Anton, @SteveHTM, and @evaldas - any idea what might be causing this error?
Shane, Senior Community Moderator
Hi @aitortomas,
If you go to the developer projects section in HubSpot, check your project’s “Builds & Deploys”, you can check the logs and either get more information about the error or see what was likely the cause by looking at the sequence of events that came before the error.
For your specific error, it might have to do something with vite, but it’s just a guess based on a quick search - your logs should provide more insight.
Hope this helps!
Thanks for sharing the screenshots.
As you mentioned, the logs do not provide additional details on the error, but overall guessing it might have something to do with a dependecy causing a timeout during a build.
One thing you could try is removing the dependencies in the project’s package.json, then introduce them one by one and see whether any specific one causes the hang up.
It might still be a HubSpot infra issue at the end of the day, but thay might at least get you closer to an aswer of what could be causing it and that information might also help HubSpot troubleshoot on their end.
Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.
The issue was an issue in the Hubspot infrastructure. In the Slack dev channel other people had the same type of errors:
✖ ERROR There were errors building this component:
- An error occurred while building project: xxxx-project.
Error: RPC error from com.hubspot.js.renderer.orchestration.rpc.JsRendererBuildExecutorRpc#invokeBuild->ChirpInternalError[DEADLINE_EXCEEDED]
✖ ERROR There were errors building this component:
- Lambda function creation failed: com.hubspot.lambda.models.errors.LambdaFunctionError: Failed to create AWS Lambda function: Unexpected error: TimeoutException
The build failed due to an internal error with id XXX. Try uploading it again. If the problem persists, contact HubSpot support with the error id.
I knew it already when I posted here.
I tried to open a Support ticket and they told me to come here as Developer Tools are unsupported with normal support. Even though multiple people reported it in Slack, we were told to come here and write here.
Of course this was a waste of time (thanks @evaldas for stepping in, but I knew it had nothing to do with my project). I learned that this Community is CSM run and that first the experts are triggered to help even though clearly no one was capable to fix something which was related to Hubspot’s infrastructure.
The issue fixed on its own (or someone fixed it silently) but no one from Hubspot addressed it proactively with me. There were no traces of any downtime in Hubspot status page for the Developer Tools section even though it was not possible to build projects for at least 2 hours (maybe more).
What I am trying to say with all of this is that the whole Hubspot CMS React is not production ready. Having such sensitive product (it affects public facing website’s in most cases) and not providing real support makes it extremely risky. I can fully understand that custom code cannot be supported (great use case for a Community). I cannot understand I have to open a Community post to raise an infrastructure issue. Hubspot is confusing peer communities with product support (I guess intentionally).
This will get lost in the sea of posts and replies, but at least I wanted to give candid feedback.
Hey @aitortomas,
Thank you for taking the time to provide this context and feedback! I sincerely apologize for the back and forth, and I hope that we can mitigate this type of situation in the future.
I’ve made sure to pass this feedback along to the team internally for now.
Shane, Senior Community Moderator