🐛 BUG: [ERROR] service core:user:worker: Uncaught TypeError: Invalid URL string. #7265
Comments
|
Getting a similar error when deploying a function to Cloudflare 19:23:54.615 | Found Functions directory at /functions. Uploading.
-- | --
19:23:54.622 | ⛅️ wrangler 3.76.0
19:23:54.622 | -------------------
19:23:55.871 | ✨ Compiled Worker successfully
19:23:55.917 | Validating asset output directory
19:23:57.554 | Deploying your site to Cloudflare's global network...
19:24:01.343 | Uploading... (19/19)
19:24:01.344 | ✨ Success! Uploaded 0 files (19 already uploaded) (0.46 sec)
19:24:01.344 |
19:24:01.687 | ✨ Upload complete!
19:24:03.367 | Success: Assets published!
19:24:05.004 | Error: Failed to publish your Function. Got error: Uncaught TypeError: Invalid URL string. at functionsWorker-0.8204575732284836.js:46232:25 in products/products.route.js at functionsWorker-0.8204575732284836.js:5:59 in __init at functionsWorker-0.8204575732284836.js:46268:5 in products/index.js at functionsWorker-0.8204575732284836.js:5:59 in __init at functionsWorker-0.8204575732284836.js:46277:5 in ../../../pages/build_tool/js/.wrangler/tmp/pages-u2mHuu/functionsRoutes-0.967709881045554.mjs at functionsWorker-0.8204575732284836.js:5:59 in __init at functionsWorker-0.8204575732284836.js:46298:1My hunch is that the issue is related to usage of However, unlike Netlify, there seems to be no way to opt-out of bundling with esbuild that I can find, other than through the CLI and the I would love to be able to do through wrangler.toml, but it seems like that is not supported - #6434 ? For example, with Netlify I can do this in their netlify.toml and nothing will get processed. [build.processing]
skip_processing = trueThe same code works fine on Vercel using their Build Output API. (I'm basically testing the same code sample across all hosting providers) |
|
hi @niklasfjeldberg and @thescientist13, Thank you for raising this issue with us. Any chance one of you can provide us with some minimal reproduction 🙏 ? I'm not able to reproduce the error you're seeing locally, so that would really help us narrow things down <3 |
CarmenPopoviciu
added
the
awaiting reporter response
|
Hey @CarmenPopoviciu 👋 Here's a repro repo I made that has a couple minimal functions that work And then in this PR I added another function using Hope that helps, and let me know if you need any more info. |
|
ah, this is fantastic!! thank you so much @thescientist13 🙏 . Going to have a look at this tomorrow morning, and see what's going on |
CarmenPopoviciu
added
the
awaiting Cloudflare response
emily-shen
removed
the
awaiting reporter response
|
My apologies for taking so long to reply. I did look into it and I can confirm that I am seeing the same when following your reproduction steps (thx again for that amazing repro At first, I too thought it might be an I'm afraid that for now there's not much more I can advise here, other than wait until this feature is implemented in the runtime :( |
CarmenPopoviciu
removed
the
awaiting Cloudflare response
|
oh, and one more thing...
for this setup specifically, it is indeed not possible to opt out of esbuild. But generally speaking, opting out of esbuild is complicated for Pages, and not something we provide a public contract for atm. Workers on the other hand do support that via Custom Builds |
|
I'm sorry I couldn't help more for now. Let me know if you have any follow-up questions. In the meanwhile I'll go ahead and close this issue, since the relevant body of work is not tracked in this repository. Once that work lands in |
|
Thanks for taking a look @CarmenPopoviciu !
As far as I can tell, I could only find a way to do that via the CLI. Is there anyway to do that with a wrangler.toml? I had referenced this issue which seems to indicate it is not? Not sure if you can confirm or not.
Ah bummer. Is there an issue to follow along with that does track this work? edit: I think I found the relevant issue - cloudflare/workerd#2963 |
|
hi @thescientist13,
If you mean for Pages, unfortunately the answer is no.
That issue you linked in there, is precisely the one! |
|
Great, thanks for all your help @CarmenPopoviciu 🙏 |
Which Cloudflare product(s) does this pertain to?
Pages
What version(s) of the tool(s) are you using?
3.87.0
What version of Node are you using?
22.11.0
What operating system and version are you using?
Linux (WSL)
Describe the Bug
Observed behavior
I have made a website with Nuxt 3 (v3.14.159) and when I try to run the website locally as CF Pages (also the same error on Cloudflare Pages own servers) I get the following error:
[ERROR] service core:user:worker: Uncaught TypeError: Invalid URL stringThe error log is not helpful for me as I am unable to locate and find out whats wrong.
Expected behavior
It should not give an error.
Steps to reproduce
I am not able to provide a public repo or minimal working code, but can provide the repo to the devs here. If no one else have any helpful advice.
This is how my
wrangler.tomlfile looks like:Commands used to build and start the server:
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
The text was updated successfully, but these errors were encountered: