1. Remix with Vite currently relies on Wrangler's getPlatformProxy() that uses miniflare under the h

Remix with Vite currently relies on Wrangler's getPlatformProxy() that uses miniflare under the hood. This setup means Remix is running on Node.js and accessing the Env through HTTP getPlatformProxy().
By following this PR, you can leverage more features specifically designed for Cloudflare Workers, remix with cloudflare pages will have bumpy journey ahead
Run the following commands to set up your development environment:
- ```
remix vite:dev
```
  remix vite:dev
```
remix vite:dev
```
  remix vite:dev
  on port 3000
- ```
wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.ts
```
  wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.ts
```
wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.ts
```
  wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.ts

Note:

worker.ts

worker.ts

worker.ts

worker.ts should be ESM-based for Cloudflare Workers.

wrangler dev

wrangler dev

enables you to develop queues, crons, and workflows within

workerd

workerd

workerd

workerd environment instead of NodeJS.

the error you're encountering is because

getPlatformProxy()

getPlatformProxy()

getPlatformProxy()

getPlatformProxy() doesn’t work with workflows. If you have

[[workflows]]

[[workflows]]

[[workflows]]

[[workflows]] in wrangler.toml, Miniflare will refer to it, resulting in the error

the development experience for a Vite-powered app has limitations, especially with newer features. This should improve once Vite v6 is released, and Wrangler is updated to support it

Zzuegno Hello, I'm really excited to try Workflows. I tried to add a Workflow to a Remix...

Matt Silverlock•10/30/24, 1:53 PM

You will need to deploy a Worker with your Workflow; you can’t bundle it into your Pages (Remix) app.

DiamondDragon•10/30/24, 4:12 PM

I'm getting a Type instantiation is excessively deep and possibly infinite.Type instantiation is excessively deep and possibly infinite. in a step. I don't think it's a very complex type being returned

DDiamondDragon noticing if you have a long output in the trace online it will go off screen (co...

Diogo Ferreira•10/30/24, 5:24 PM

Thanks for reporting it!

Avi•10/30/24, 11:24 PM

is there support for scheduling a workflow to run periodically, like a cron job?

Avi•10/30/24, 11:24 PM

or would I use a worker with a cron trigger to initiate a workflow?

Avi•10/30/24, 11:24 PM

oh the docs address this, yes, nvm

Avi•10/30/24, 11:28 PM

ok in that case

Jacob•10/30/24, 11:28 PM

If you want to run it more often than once a minute, you could have your workflow schedule its next run rather than an external trigger. Would just need to jump-start it initially

Avi•10/30/24, 11:28 PM

what does the workflow concurrency limit mean? does that mean that if I have 5k scheduled, 100 will be initally scheduled to run, and as they conplete,m ore will be scheduled?

Avi•10/30/24, 11:28 PM

basically 100 max parallelism?

JJacob If you want to run it more often than once a minute, you could have your workflo...

Avi•10/30/24, 11:29 PM

my usecase is that i'd like to run code every night at midnight, and id love to NOT have to create a separate cloudflare worker with a scheduledscheduled handler for this

Avi•10/30/24, 11:29 PM

just one instance of that code

Avi•10/30/24, 11:29 PM

essentially a global singleton

Jacob•10/30/24, 11:29 PM

The same Worker can export both the scheduled handler and the Workflow

Jacob•10/30/24, 11:30 PM

So it can all be in one .ts file

JJacob The same Worker can export both the scheduled handler and the Workflow

Avi•10/30/24, 11:30 PM

yeah, but that worker is actually just a DO stub wrapper

Jacob•10/30/24, 11:31 PM

wdym?

Avi•10/30/24, 11:31 PM

i guess we could do it there though

JJacob wdym?

Avi•10/30/24, 11:31 PM

i mean the "worker" is literally just the minimum boilerplate/wrapper to wrap a DO stub

Avi•10/30/24, 11:31 PM

but that doesnt mean we cant add a cron scheduled handler to it

Jacob•10/30/24, 11:33 PM

Yeah I’d just put the scheduled handler in the same worker that you’re wanting to trigger Workflows from

Jacob•10/30/24, 11:39 PM

Another trick I’ve found with crons (in general) that hit external APIs is to not schedule right at the top of the hour - some APIs I’ve used can actually slow down a bit because of everyone’s crons hitting them at the exact same time

skip•10/31/24, 4:37 AM

Can a workflow codebase co-exist inside a Pages repo?

Sskip 👋 Can a workflow codebase co-exist inside a Pages repo?

fry69•10/31/24, 4:41 AM

wrangler will deploy those to different entities in Cloudflare, so it should not matter where they reside on your side.

fry69•10/31/24, 4:42 AM

You might face problems linking such a repo from the dashboard though, maybe it still works with custom build commands?

Avi•10/31/24, 5:06 AM

it looks like

workerd

workerd

crashes when more than a single workflow is defined in

wrangler.toml

wrangler.toml

Avi•10/31/24, 5:08 AM

ah yeah i see this discussed above

AAvi it looks like `workerd` crashes when more than a single workflow is defined in `...

fry69•10/31/24, 5:09 AM

It should be possible to use separate

wrangler.toml

wrangler.toml

files in separate directories and invoke wrangler separately in those directories with npm scripts.

fry69•10/31/24, 5:10 AM

Maybe even go full monorepo

Ffry69 It should be possible to use separate `wrangler.toml` files in separate director...

Avi•10/31/24, 5:10 AM

but how would those get deployed?

Avi•10/31/24, 5:10 AM

i'd want them tied to the worker i'm deploying with the main

wrangler.toml

wrangler.toml

AAvi but how would those get deployed?

fry69•10/31/24, 5:10 AM

To different Cloudflare names/entities?

Avi•10/31/24, 5:11 AM

i'm not trying to change our deployed infra to workaround a wrangler bug lol

Avi•10/31/24, 5:11 AM

i'm just gonna comment one out at a time

AAvi it looks like `workerd` crashes when more than a single workflow is defined in `...

DiamondDragon•10/31/24, 5:30 AM

ugh i spent like an hour today trying to figure out why i could get the worker server to start... added a 2nd test workflow to play around

Avi•10/31/24, 5:33 AM

yeah it’s rough. imo they should have added a note in the changelog or something

DiamondDragon•10/31/24, 5:36 AM

is it possible to inspect a workflow triggered locally?

Avi•10/31/24, 5:36 AM

i’d also love to know this

DiamondDragon•10/31/24, 5:37 AM

running nr wrangler workflows instances describe test latestnr wrangler workflows instances describe test latest shows the last deployed instance

Mm0c I have a question how workflows are "versioned' Lets say a workflow has 3 steps ...

fry69•10/31/24, 6:00 AM

Running workflows will not get updated of course, only freshly instantiated workflows will run the new deployed version.

DiamondDragon•10/31/24, 6:28 AM

Not sure if this is silly - does it make ense to use a RPC service binding in a workflow/step? getting TypeError: Cannot read properties of undefined (reading 'TEST_SERVICE') TypeError: Cannot read properties of undefined (reading 'TEST_SERVICE') when just testing around

bkyerv•10/31/24, 6:46 AM

is workflows accessible/supported from inside pages functions?

bkyerv•10/31/24, 6:46 AM

I mean directly via env.[workflow_name] e.g. from astro project. i.e. not via network like fetch(...)

Advany•10/31/24, 9:07 AM

I can't seem to figure out, how do I limit the amount of instances per minute a workflow can ingest? I have browser rendering working inside of the workflows and I want to limit it to only do around 1 instance per 10 seconds orso

bkyerv•10/31/24, 9:21 AM

an attempt to delete a workflow from the cli results in an error saying it failed. in the dashboard I have already deleted connected worker but the workflow itself doesn't get deleted regardless of how many times I try to delete it by way of

wrangler workflows delete workflows-starter

wrangler workflows delete workflows-starter

Bbkyerv an attempt to delete a workflow from the cli results in an error saying it faile...

fry69•10/31/24, 9:26 AM

Deleting Workflows is still not possible as far as I know -> workflows

bkyerv•10/31/24, 9:28 AM

why then do they keep this in their docs. thank you for pionting it out though

Bbkyerv why then do they keep this in their docs. thank you for pionting it out though

fry69•10/31/24, 9:30 AM

Nobody told the docu team I guess

Ffry69 Nobody told the docu team I guess 🙂

Advany•10/31/24, 9:53 AM

its a beta... just opened up... lets be kind that they didn't wait till everything was polished

1. Remix with Vite currently relies on Wrangler's getPlatformProxy() that uses miniflare under the h

Similar Threads

Similar Threads

Similar Threads