{"id":1412,"date":"2025-09-17T16:25:37","date_gmt":"2025-09-17T16:25:37","guid":{"rendered":"http:\/\/gogetmuscle.com\/?p=1412"},"modified":"2025-09-17T17:40:57","modified_gmt":"2025-09-17T17:40:57","slug":"hubspot-project-builder-often-fails-for-random-reasons","status":"publish","type":"post","link":"http:\/\/gogetmuscle.com\/index.php\/2025\/09\/17\/hubspot-project-builder-often-fails-for-random-reasons\/","title":{"rendered":"HubSpot project builder often fails for random reasons"},"content":{"rendered":"
I’ve got a legacy app on platform v2023.2<\/SPAN><\/P> Every time I upload it to HubSpot to build then it fails for some random reason. If I upload any previous commit that was working it still fails. An example error is But the specific error is not really important – it was working before but now\u00a0cms-js-build doesn’t work, the build system seems to be stateful and broken. And if you manage to get this error to go away you’ll always get a new one. We’ve tried many AI fixes from HubSpot agent or ChatGPT etc. \u00a0<\/P> However, very occasionally the build does work, for exactly the same code\/commit that fails previously. But it’s random. It’s like there’s one HubSpot build agent that works with our project and the rest don’t for some reason.<\/SPAN><\/P> \u00a0<\/P> \u00a0<\/P> I’ve tried raising this issue with support but they’ve sent me here.<\/SPAN><\/P> \u00a0<\/P> The painful thing is now we have an issue in production which I can’t even look at fixing because I can’t get builds working. All despite not changing any code. And our customers are upset.<\/SPAN><\/P><\/p>\n","protected":false},"excerpt":{"rendered":" I’ve got a legacy app on platform v2023.2Every time I upload it to HubSpot to build then it fails for some random reason. If I upload any previous commit that was working it still fails. An example error is[ERROR] Sep 08 11:09:27AM BST [vite]: Rollup failed to resolve import “@kurkle\/color” from “\/tmp\/cms_zVmz8S\/cms-js-build\/node_modules\/chart.js\/dist\/chart.js”. [ERROR] Sep 08 […]<\/p>\n","protected":false},"author":1,"featured_media":1414,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"_links":{"self":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/1412"}],"collection":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/comments?post=1412"}],"version-history":[{"count":2,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/1412\/revisions"}],"predecessor-version":[{"id":1415,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/1412\/revisions\/1415"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/media\/1414"}],"wp:attachment":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/media?parent=1412"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/categories?post=1412"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/tags?post=1412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/SPAN><\/P>[ERROR]
\n Sep 08 11:09:27AM BST [vite]: Rollup failed to resolve import “@kurkle\/color” from “\/tmp\/cms_zVmz8S\/cms-js-build\/node_modules\/chart.js\/dist\/chart.js”.
\n[ERROR]
\n Sep 08 11:09:27AM BST This is most likely unintended because it can break your application at runtime.
\n[ERROR]
\n Sep 08 11:09:27AM BST If you do want to externalize this module explicitly add it to
\n[ERROR]
\n Sep 08 11:09:27AM BST `build.rollupOptions.external`
I’ve tried creating new projects but that doesn’t fix it. Tried using platform 2025.1 and that doesn’t fix it.<\/SPAN><\/P><\/span><\/P>