apolodoro
apolodoro
Explore posts from servers
CDCloudflare DevelopersHHono
PostsComments
CDCloudflare Developers
Created by apolodoro on 2/17/2025 in #workers-help
Deploy Sveltekit on Workers with Bun
Solved - Remember to add "bun run build" specifically as your build command
2 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
I'll try right away
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
Uuuu
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
Nope and no luck pinging...
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
@DaniFoldi sorry for the ping but im not sure how to ask for help since no one from the team apparently saw this thread...
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
Should i specify anything other than bun run build for the cloudflare build command?
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
I can build and deploy to cloudflare locally the problem is when cloudflare has to run the build
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
It does not fail locally
15 replies
CDCloudflare Developers
Created by apolodoro on 1/22/2025 in #workers-help
Deploying sveltekit monorepo
And this is the app package.json
15 replies
CDCloudflare Developers
Created by apolodoro on 11/12/2024 in #workers-help
Unknown error 10013
Yep just tried, and still the same on the latest version of wrangler
12 replies
CDCloudflare Developers
Created by apolodoro on 11/12/2024 in #workers-help
Unknown error 10013
#:schema node_modules/wrangler/config-schema.json
name = "backoffice"
compatibility_date = "2024-11-06"
main = ".svelte-kit/cloudflare/_worker.js"
# Disabled assets to be able to use wrangler dev --remote
# assets = { directory = ".svelte-kit/cloudflare", binding = "ASSETS" }

# Workers Logs
# Docs: https://developers.cloudflare.com/workers/observability/logs/workers-logs/
# Configuration: https://developers.cloudflare.com/workers/observability/logs/workers-logs/#enable-workers-logs
[observability]
enabled = true


[[d1_databases]]
binding = "DB"
#:schema node_modules/wrangler/config-schema.json
name = "backoffice"
compatibility_date = "2024-11-06"
main = ".svelte-kit/cloudflare/_worker.js"
# Disabled assets to be able to use wrangler dev --remote
# assets = { directory = ".svelte-kit/cloudflare", binding = "ASSETS" }

# Workers Logs
# Docs: https://developers.cloudflare.com/workers/observability/logs/workers-logs/
# Configuration: https://developers.cloudflare.com/workers/observability/logs/workers-logs/#enable-workers-logs
[observability]
enabled = true


[[d1_databases]]
binding = "DB"
12 replies
CDCloudflare Developers
Created by apolodoro on 11/12/2024 in #workers-help
Unknown error 10013
I disabled assets to be able to use remote but thats when i got the error
12 replies
CDCloudflare Developers
Created by apolodoro on 11/12/2024 in #workers-help
Unknown error 10013
Of course
12 replies
CDCloudflare Developers
Created by DiamondDragon on 9/30/2024 in #workers-help
Error on remote worker: APIError: A request to the Cloudflare API
(/accounts/3ee55606f881222ad1efb703537713b1/workers/scripts/backoffice/edge-preview) failed.', notes: [ { text: 'workers.api.error.unknown [code: 10013]' } ], location: undefined, kind: 'error', code: 10013, accountTag: '3ee55606f881222ad1efb703537713b1' } I am also getting an unknown error. Any idea what this code may indicate?
6 replies
CDCloudflare Developers
Created by apolodoro on 10/25/2024 in #workflows-beta
Events
And how would that nesting work? By triggering new workflows within workflows? Por cierto gracias por la rapidez en la respuesta!
3 replies
CDCloudflare Developers
Created by apolodoro on 3/13/2024 in #general-help
TLS issue - WORKER to AWS IoT Core
Actually the solution did work! It was a fault in my code that i didint change back after testing... I changed the description so that if someone stumbles here understands that it works now
21 replies