My "need to" is primarily when a specific (often non-web) application requires me to. For example, t

My "need to" is primarily when a specific (often non-web) application requires me to. For example, the other day I wrote a custom extension for Raycast (https://www.raycast.com/) and they require React.

HHello, I’m Allie!Region: Moon, coming :soontm: /j

Chaika•3/13/25, 2:38 PM

Deployed to the Milky way galaxy

Isaac McFadyenOP•3/13/25, 2:38 PM

I definitely never use it for web if I can :lul:

Silvan•3/13/25, 2:39 PM

but muh vdom muh “use server”

CChaika Deployed to the Milky way galaxy

Hello, I’m Allie!•3/13/25, 2:39 PM

You are thinking too small. We will weave CF into the fabric of the universe, so you can run Workers on every electron

Silvan•3/13/25, 2:39 PM

whats the atom limit of a single worker instance?

SSilvan whats the atom limit of a single worker instance?

Hello, I’m Allie!•3/13/25, 2:40 PM

Infinite

IIsaac McFadyen My "need to" is primarily when a specific (often non-web) application requires m...

RobbBoss•3/13/25, 2:40 PM

Ah, I was in this scenario with Tina CMS and decided that since they didn't make it easy to write a webcomponent to replace their react component, I abandonded that CMS option. It's frustrating when devs pigeonhole us into React, but that's a fair use case. It's so cumbersome how it literally invites facebook into your entire codebase.

Silvan•3/13/25, 2:40 PM

i have not had a single good experience with a cms ever i cant lie

RobbBoss•3/13/25, 2:41 PM

Drupal 5 and 6 were awesome. long ago.

SSilvan i have not had a single good experience with a cms ever i cant lie

Hello, I’m Allie!•3/13/25, 2:41 PM

This is why a CMS should just be a folder of markdown

HHello, I’m Allie!This is why a CMS should just be a folder of markdown

Silvan•3/13/25, 2:41 PM

yep unironically

Hello, I’m Allie!•3/13/25, 2:41 PM

But also, #off-topic (definitely also me doing it)

Silvan•3/13/25, 2:42 PM

workers + r2 perfect cms

Evorage•3/13/25, 2:42 PM

is pages really dead? should I avoid it for future projects?
Deployment Failed... Why?

HHello, I’m Allie!This is why a CMS should just be a folder of markdown

RobbBoss•3/13/25, 2:43 PM

Bringing it back on-topic, this is how I wound up at Astro on Workers forever ago. I basically had been building a KV CMS and then Astro fit the bill on workers/pages

Tincan•3/13/25, 2:43 PM

hi guys, i used to use this command "npx wrangler pages dev -- yarn dev" but its being deprecated and has started having resource locked errors.

New command might be something like "npx wrangler pages dev .output/public --live-reload" but this isn't ideal as I still have to run yarn generate after changes to templates in my nuxt project, as output/plublic is not automatically updated when templates change. This is hugely slowed down workflow so I'm wondeing what the better approach is

EEvorage is pages really dead? should I avoid it for future projects? https://discord.com...

Isaac McFadyenOP•3/13/25, 2:46 PM

I'll refer you to this, but TLDR: not officially but kinda. workers-and-pages-discussions

Isaac McFadyenOP•3/13/25, 2:47 PM

Workers Assets is the recommended way going forward.

Evorage•3/13/25, 2:48 PM

thank you, it might beneficial to have a message on the dash when creating a pages project

Silvan•3/13/25, 2:49 PM

well it will still work for ages thats why they dont want to do that i think

Isaac McFadyenOP•3/13/25, 2:49 PM

Yeah that's mainly why I said it's not "officially" deprecated; it's still usable, but likely won't receive any new improvements.

Evorage•3/13/25, 2:51 PM

sort of "end of life"

Silvan•3/13/25, 2:54 PM

theres barely any features missing other than preview links for branches anyway

SSilvan well it will still work for ages thats why they dont want to do that i think

RobbBoss•3/13/25, 3:07 PM

I've given this a lot of thought, because I personally just lost a bunch of time due to the fact that we weren't looking in the /Public directory... and you just saved our butts, by the way.
Just the fact that building new products on it would be a bad idea (tm) is enough to warrant some kind of deprecation notice.

I said somewhere else, Python was deprecating Python 2 for over 10 years. It was important to make the notice, even if support would continue for a long time.

IIsaac McFadyen Yeah that's mainly why I said it's not "officially" deprecated; it's still usabl...

RobbBoss•3/13/25, 3:08 PM

This unofficial deprecation is equivalent to uncertainty in the platform and that is bad.

Silvan•3/13/25, 3:09 PM

I think a recommendation would be enough. but its a beta.

my guess? static assets stable with the next dev week

RobbBoss•3/13/25, 3:10 PM

Yeah, realizing that Workers Assets is still beta, I'm guessing that is why there has not been much notice. But they went ahead and recategorized everything and began name changes, and changing the menu around is kind of a hugely alarming notice to almost every user that things are changing, and without canonical word, that is uncertainty and is patently bad.

RobbBoss•3/13/25, 3:11 PM

Like having to explain this all to investors yesterday morning was not fun.

Tincan•3/13/25, 3:25 PM

guys any advance on how to adapt this command so that i dont have to manually rebuild output folder each time to reflect changes. Surely its possible

npx wrangler pages dev .output/public

TTincan guys any advance on how to adapt this command so that i dont have to manually re...

RobbBoss•3/13/25, 3:28 PM

like you want a watch style function or? I guess one option could be to literally use watchwatch to watch the dir for changes and trigger a rebuild automagically

RRobbBoss like you want a watch style function or? I guess one option could be to literall...

Tincan•3/13/25, 3:31 PM

Well it doesn't make sense just to watch the public folder because its not rebuild every time you change a template in a nuxt project, only when you run yarn generate.

Formerly you could run a proxy command as a flag on the wrangler command that ran yarn dev, but this isnt allowed in wrangler v4
"npx wrangler pages dev -- yarn dev"

Evorage•3/13/25, 3:36 PM

is it possible to see the log of a deployed pages app?

Evorage•3/13/25, 3:37 PM

i keep getting a 500 error and I don't know why

RobbBoss•3/13/25, 3:38 PM

my understanding of the ---- flag is that it is an npm specifc flag indicating the end of options for npm specific commands, such that in the case you mentioned that

yarn dev

yarn dev

becomes a command line option for the wrangler pages devwrangler pages dev command. In that case, my next step would probably be to figure out if there is a flag on this page that does what you are looking for: https://developers.cloudflare.com/workers/wrangler/commands/#dev

I'm, personally, still unclear on what you need done that can't be done with a well-placed watchwatch since that is typically how these things work anyways, but that is where I would look if I better understood the specifics of your needs.

Cloudflare Docs

Commands - Wrangler · Cloudflare Workers docs

Create, develop, and deploy your Cloudflare Workers with Wrangler commands.

TTincan Well it doesn't make sense just to watch the public folder because its not rebui...

Hard@Work•3/13/25, 3:49 PM

IIRC they removed it because it had bad UX. It still couldn't run Workers, so all you would have is what

yarn dev

yarn dev

would output anyway

Hard@Work•3/13/25, 3:50 PM

The new recommendation once it lands in more frameworks is to use the new Vite Environments API, which means that frameworks can now run their dev server in

workerd

workerd

, with all of the bells and whistles that a Worker would have

EEvorage is it possible to see the log of a deployed pages app?

Walshy•3/13/25, 5:35 PM

wrangler pages deployment tail

Silvan•3/14/25, 1:18 PM

i could see d1 replication next month on dev week. containers? maybe not

RobbBoss•3/14/25, 2:22 PM

Weird question... when making a new Workers project from a github repository, what if I don't want to deploy to workers.dev?
Reason being, it seems that tons of bots just watch for deployments to workers.dev and jump at the opportunity to ping your Worker. :/

RRobbBoss Weird question... when making a new Workers project from a github repository, wh...

zegevlier•3/14/25, 2:31 PM

You can disable your workers.dev domain before you deploy in your wrangler.toml/jsoncwrangler.toml/jsonc. https://developers.cloudflare.com/workers/configuration/routing/workers-dev/#disabling-workersdev

Chaika•3/14/25, 2:55 PM

Bots should only be from the cert. issuance for *.workername.subdomain.workers.dev anyway, if you deploy and snipe off the workers.dev quick off, should avoid it

Chaika•3/14/25, 2:55 PM

for functions?

Chaika•3/14/25, 2:55 PM

there's frameworks which can emulate that

Chaika•3/14/25, 2:57 PM

yea, eh, I imagine it's one of those things where the vast majority of people use frameworks anyway
I wonder how they're going to try to make that migrate to workers assets

Chaika•3/14/25, 2:58 PM

they said in the blog post:

We plan to bridge the gaps between Workers and Pages and provide ways to migrate your Pages projects to Workers.

Chaika•3/14/25, 2:59 PM

idk how you'd migrate file path routing without having something to deal with it

Chaika•3/14/25, 2:59 PM

maybe just a compat framework or something lol pages-legacy-routingpages-legacy-routing

CChaika Bots should only be from the cert. issuance for *.workername.subdomain.workers.d...

Hello, I’m Allie!•3/14/25, 3:18 PM

You know what would be a real cool and dumb feature for custom domains? Pre-warming. I.e., you activate the domain, issue the cert, but block every request for the first n-minutes

HHello, I’m Allie!You know what would be a real cool and dumb feature for custom domains? Pre-warm...

Chaika•3/14/25, 3:20 PM

lol I think you can already do that yourself

My "need to" is primarily when a specific (often non-web) application requires me to. For example, t

Similar Threads

Similar Threads

Similar Threads