Closed whilefoo closed 8 months ago
I've managed to run Miniflare but it shows some weird C++ errors whenever a request comes so we'll have to run Miniflare with wrangler v3 and run smee client separately.
I think yarn plug and play can be disabled either directly with a yarn config property or by using a different version of yarn. Perhaps that will help?
I did brief research now on both frameworks:
Why can't we just go raw and use neither?
Miniflare can be used as a standalone library or as part of wrangler. And yes it's used for development when you're developing a Cloudflare worker. Basically when you run wrangler dev
it runs Miniflare which simulates a Cloudflare worker environment.
I wanted to run Miniflare as standalone so we can run smee together, but since it's not working we will just have to run two commands, one to start smee and one to start wrangler dev server.
Also we don't need esbuild because wrangler dev
and wrangler deploy
automatically do everything, you just need to provide the JS/TS file.
With the latest commit I got the POC to work, it works by running a dev server and also by deploying to Cloudflare.
Can't get this to work at https://github.com/ubiquibot-pavlovcik/ubiquibot-sandbox/issues/1
There are actually two options:
I'm currently testing out the first option and it works when I build the worker but not when I build the local server because of some weird errors: