FIX FOUND Deployment failed Qwikjs
b43165e8.dom-cogan.pages.dev
a64efbd7163580ac72aa0029a4c264c6
not sure what happened but i use npm run deploy everything says its successful when i run it locally it works but on my cloudflare dashboard it says no deployment found. I even uploaded the files myself and it still says deployment found.
25 Replies
What do you see when you hit View Details?
ive had the same enviorment variable from the very first deployment. they were not being used but now they are
Just to check, do you have a support ticket open? It is fine if you don't
@Dom Cogan What were the nature of the changes between the deployments? Were these just changes to your project files? You don't need to go into detail.
Just trying to understand what changes were made
I don’t.
If you visit the website and go to /blog in the deployment that went through it static text but now I’m trying to get a list from my database
Okay one moment.
Did you have failures prior to the last stretch of successful deployments?
or deployment if this was just the one.
Kinda same issue, thought I was doing something wrong so I started over added back on thing at a time until it failed
Since I restarted the project no, I’ve had no other deployments fail until trying to use my database
So, what I can say is that this is probably an error within one of the modules you're using. This is not anything relating to Cloudflare infrastructure. I can't really disclose much more as this is public forum but I would have a check on the modules you're adding and also check the buiild logs on the specific deployments if you can locate these.
Cloudflare Docs
Debugging Pages · Cloudflare Pages docs
When setting up your Pages project, you may encounter various errors that prevent you from successfully deploying your site. This guide gives an …
There’s likely an internal userland error which isn’t surfaced to the user here. They’ll only see vague internal error references. Providing the error would be super helpful.
The only error I get when deploying is about warning about nodejs-compat for wranglers. How can I get this error to share?
Is this something that I would be able to see when I do the npm run biuild or npm run deploy?
You might be able to see it after you build and run with
pages dev
But if you just upload, there's no way for you to see errors like this, no.Typically I run the npm run build then do npm run deploy. The only reason I uploaded the files directly was to test if it was a problem with the npm run deploy script
If you try running with
wrangler pages dev, you might be able to find the error locally.when i run i get.
Uncaught ReferenceError: window is not defined
at null.<anonymous> (ftsh1voktru.js:114:22) in
../node_modules/isomorphic-form-data/lib/browser.js
at null.<anonymous> (ftsh1voktru.js:52:50) in __require22
at null.<anonymous> (ftsh1voktru.js:4427:43)
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
Aha, there you go. Something you're loading is trying to access
window which doesn't exist in Workers
It looks like isomorphic-form-dataIm not using isomorphic-form-data
Something you're importing is
Try
npm ls isomorphic-form-data and you might find which package is loading itThank you for your help thus far, how can i add that to the worker? my database needs it which is probably why its failing.
You can't,
window doesn't exist in Workers. What are you trying to do exactly? You'll likely need to find an alternate solutionI’m trying connect my /blog page to display a list from my database. My database in the background is using the form data would looking at the full code help?
Yes sure. It sounds like whatever package you're using to talk to your DB is doing this, and that won't work sadly
GitHub
GitHub - Dom-Cogan/Dom-Cogan: My personal Blog
My personal Blog. Contribute to Dom-Cogan/Dom-Cogan development by creating an account on GitHub.
Ok so In QWik i was using useTask() however this still didnt work when i change it to useVisable task i can now deploy.... locally still but like with wrangler pages dev i can load my website and it works perfectly fine but when i deploy it to cloud flare i am still getting the error