TheNeur0mancer
CDCloudflare Developers
•Created by Ercan on 4/10/2024 in #pages-help
Failed: Pages deployments stopped working
I do specify all of the following in my deployments:
GO_VERSION HUGO_VERSION NODE_VERSION NPM_VERSION ... and have a package.json/lock for a otherwise Hugo driven project. The build process that actually runs is "npm run blah-blah" however as the original poster described above, the error appears just after cloning (before tools are even installed)
GO_VERSION HUGO_VERSION NODE_VERSION NPM_VERSION ... and have a package.json/lock for a otherwise Hugo driven project. The build process that actually runs is "npm run blah-blah" however as the original poster described above, the error appears just after cloning (before tools are even installed)
34 replies
CDCloudflare Developers
•Created by Ercan on 4/10/2024 in #pages-help
Failed: Pages deployments stopped working
It "seems" like the "error" is more of a "warn". but I'm not sure.
34 replies
CDCloudflare Developers
•Created by Ercan on 4/10/2024 in #pages-help
Failed: Pages deployments stopped working
So, I have a Hugo site and have used NPM to manage it - this adds a couple of interesting management features which Hugo alone lacks.
Possibly, i haven't noticed the error until just now, i update my site about once per month... but the message above seems to indicate that the presence of package.json might be influencing this behavior. If i add a wrangler.toml (which I don't want, because i prefer "dashboard" configuration, the message goes away.
Possibly, i haven't noticed the error until just now, i update my site about once per month... but the message above seems to indicate that the presence of package.json might be influencing this behavior. If i add a wrangler.toml (which I don't want, because i prefer "dashboard" configuration, the message goes away.
34 replies