Rtrust and jquery in the same sentence 
please don't use jquery. I haven't heard a use case in 10 years. Wordpress is to blame for it's continued existence, I'm sure.
please don't use jquery. I haven't heard a use case in 10 years. Wordpress is to blame for it's continued existence, I'm sure.
RI agree with this, adding the caveat that I never need to. Even Astro's implicit embracing of React is troublesome for me.
Si was being sarcastic
HRegion: Moon, coming :soontm: /j
Sas long as it isnt mars
RI gathered. Sorry if it seemed otherwise. 
IMy "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.
CDeployed to the Milky way galaxy
II definitely never use it for web if I can :lul:
Sbut muh vdom muh “use server”
HYou are thinking too small. We will weave CF into the fabric of the universe, so you can run Workers on every electron
Swhats the atom limit of a single worker instance?
HInfinite
RAh, 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.
Si have not had a single good experience with a cms ever i cant lie
RDrupal 5 and 6 were awesome. long ago.
HThis is why a CMS should just be a folder of markdown
Syep unironically
HBut also, #off-topic (definitely also me doing it)
Sworkers + r2 perfect cms
ERBringing 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
Thi 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
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
IIWorkers Assets is the recommended way going forward.
E
thank you, it might beneficial to have a message on the dash when creating a pages projectSwell it will still work for ages thats why they dont want to do that i think
IYeah that's mainly why I said it's not "officially" deprecated; it's still usable, but likely won't receive any new improvements.
Esort of "end of life"
Stheres barely any features missing other than preview links for branches anyway
RI'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.
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.
RThis unofficial deprecation is equivalent to uncertainty in the platform and that is bad.
SI think a recommendation would be enough. but its a beta.
my guess? static assets stable with the next dev week
my guess? static assets stable with the next dev week
RYeah, 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.
RLike having to explain this all to investors yesterday morning was not fun.
Tguys 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
npx wrangler pages dev .output/public
Rlike you want a watch style function or? I guess one option could be to literally use
watchWell 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"
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"
Eis it possible to see the log of a deployed pages app?
Ei keep getting a 500 error and I don't know why 
Rmy understanding of the
I'm, personally, still unclear on what you need done that can't be done with a well-placed
--yarn devwrangler pages devI'm, personally, still unclear on what you need done that can't be done with a well-placed
watchCloudflare Docs
Create, develop, and deploy your Cloudflare Workers with Wrangler commands.
HIIRC they removed it because it had bad UX. It still couldn't run Workers, so all you would have is what
yarn devThe 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
Wwrangler pages deployment tail
Si could see d1 replication next month on dev week. containers? maybe not
RWeird 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. :/
Reason being, it seems that tons of bots just watch for deployments to workers.dev and jump at the opportunity to ping your Worker. :/
ZYou can disable your workers.dev domain before you deploy in your
wrangler.toml/jsoncBots 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
Cfor functions?
