Pete Bacon Darwin

@iSnifer @Jilles I think you might have just been unlucky. If it keeps happening please create an issue at github.com/cloudflare/wor…

@iSnifer @Jilles We had this problem a lot when we first developed create-cloudflare. We worked with the DNS team to minimize the chance of this and I have not heard of it causing problems for a couple of years.

Dear, @Jilles how can I can help to debug this freezed npm create cloudflare@latest command after successful deployment to workers.dev? A lot of lines here bc I tapped Enter a lot of times

@dctanner @uselayercode You are using the Cloudflare vite-plugin?

@petebd hey we’re making a workers vite demo for @uselayercode but no worker logs are ever shown in the console. Is this a known issues? (We’re hosting a hackathon at your offices on 23rd and wanted to get this working beforehand).

Must-read book this summer. open.spotify.com/show/08qZU5k3Z…

@Dan_The_Goodman @CloudflareDev Thanks. We'll look into it.

@petebd @CloudflareDev github.com/danthegoodman1…

@CloudflareDev your test framework with workerd and vitest just orphans nodejs(vitest) processes that consume a full core had one running for 14 days after clean test exits... no wonder my laptop was dying in 4 hours

@benankdev @MikeNomitch_CF Are you just using Vite to build the app before passing it to `wrangler pages dev` or `wrangler pages deploy`? I would have expected setting it as an external would work in that case...

Excited about this! But does it work with Pages? Getting this error when building: [vite]: Rollup failed to resolve import "cloudflare:workers" Externalizing it via build.rollupOptions.external gives this error: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. Received protocol 'cloudflare:' Any ideas on how to fix it?

Tired of threading `env` through your Worker code to access a binding? Or want to do some top-level config using an env var? This is for you: developers.cloudflare.com/changelog/2025…

@JacobMGEvans @dillon_mulroy You're way too kind 😊

@dillon_mulroy He wasn't "technically" my EM but was temporarily @petebd He cared, a lot. Made everyone on the team feel like we mattered, just a natural knack for moral & encouragement... Just leadership for that matter. I never worked on harder problems but felt like I could do them more.

good engineering managers are incredibly rare and often don’t get enough credit. who was your favorite EM and what made them amazing at their job?

@whatnicktweets @IgorMinar @CloudflareDev And we have an experimental Vite+React+API C3 template: ``` pnpx create-cloudflare@beta --experimental --framework=react ``` Give it a go and send us feedback!

@whatnicktweets @IgorMinar @CloudflareDev Yes! We've been working hard with the Vite team and other frameworks for the last 6 months on this. Check out #readme" target="_blank" rel="nofollow noopener">github.com/cloudflare/wor….

Hey! I believe Vite has this now: vite.dev/guide/api-envi… Did anyone ever figure out this super dream setup? blog.cloudflare.com/blazing-fast-d… If so, any examples or point in direction? @IgorMinar @CloudflareDev @petebd

@mpsurfate @yagiznizipli @Cloudflare Have you seen Smart Placement? developers.cloudflare.com/workers/config…

@yagiznizipli @Cloudflare Main reason is because edge computing decreases latency between the code and the user, but increases latency between code and the database. I bet it's better for db and code to have less latency and the opposite. Eventual consistency doesn't cut it.

@juristr @dotNetkow @IgorMinar 👋

@dotNetkow maybe @IgorMinar or @petebd

do i know anyone that works at cloudflare? :)

🏃@CloudflareDev Developer Week 2024 🧡 ICYMI 🧡 Speed run

Really looking forward to how we can use this to improve the developer experience when building for Cloudflare Workers/Pages.

@naveedahmed @IgorMinar @elithrar @Cloudflare @CloudflareDev But it has been great seeing @naveedahmed get full Angular SSR running on Cloudflare Pages for a substantial production site. One of the first to do so that I have come across.

@IgorMinar @elithrar @Cloudflare @CloudflareDev @petebd Yes, he indeed is very helpful. But I've yet to convince him that non-html ulrs e.g urls ending with .js, .jpg, .css should not be redirected to index.html in case of Angular SPA. This results in Soft 404 errors in Google Search Console, bad for SEO Ref: #single-page-application-spa-rendering" target="_blank" rel="nofollow noopener">developers.cloudflare.com/pages/configur…

Direct upload via @Cloudflare Pages: developers.cloudflare.com/pages/get-star… (I’ve used this more times than I would like to admit!)

@naveedahmed @IgorMinar @elithrar @Cloudflare @CloudflareDev Of course with a 404.html page this doesn't happen; but then you have to send your SPA routes via a Worker to get them to return the index.html content.

@gabrielnocode @rickyrobinett @Cloudflare @angular On thing I am aware of is that Critter (critical CSS inlining) in SSR for Angular was not working well on Cloudflare. But the starter does not use this so it should work...

@gabrielnocode @rickyrobinett @Cloudflare @angular Hi Gabriel - could you DM me so that I can work through this with you? I just tried it locally and the deployment succeeded but I might have chosen different options to you...

@Cloudflare Any idea why the @angular app from the default deployment using the cloudflare CLI isn't working? blog.cloudflare.com/making-cloudfl… CF Pages is throwing an error after deployment