is there a way to inherit all environment variables when using `wrangler dev` - currently finding th

Mmatt is there a way to inherit all environment variables when using `wrangler dev` - ...

C

Cyb3r-Jak3•6/30/23, 2:22 AM

Wrangler will read from

wrangler.toml

wrangler.toml

for

wrangler dev

wrangler dev

and you can use a

.dev.vars

.dev.vars

.dev.vars

.dev.vars file

M

mattOP•6/30/23, 5:48 AM

I'm trying to build a local dev environment, and managed to get wrangler dev working for a single script, but I now need to recreate the prod-like routes with multiple scripts. Does wrangler dev support running multiple scripts, each with its own route, e.g.

my.local/foo/* -> scripts/foo.js

my.local/foo/* -> scripts/foo.js

my.local/foo/* -> scripts/foo.js

my.local/foo/* -> scripts/foo.js

my.local/bar/* -> scripts/bar.js

my.local/bar/* -> scripts/bar.js

my.local/bar/* -> scripts/bar.js

my.local/bar/* -> scripts/bar.js
etc...

the only idea I have so far is to do the routing myself, where the handler will:
- check for presence of matching script
- start the wrangler dev process, incl port selection
- proxy the request through to the associated process/port
- use a process manager to kill process after idle timeout

M

mattOP•6/30/23, 6:26 AM

Ah it looks like I may need to use miniflare directly?

M

mattOP•6/30/23, 7:37 AM

i tried using

workers

workers

workers

workers but couldn't get live reload working... plus the contents of /scripts/ can change during development, so what I ended up with is not perfect but it's good enough for local dev:

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

Original message was deleted

M

MrBBot•6/30/23, 12:43 PM

Hey!

Unfortunately Miniflare doesn't implement the S3 API for R2, so you'll only be able to upload via the worker bindings locally.

Original message was deleted

M

MrBBot•6/30/23, 12:44 PM

We haven't implemented support for using remote R2 buckets in local mode. We had previously implemented this for KV, but it was incompatible with some changes we made to Miniflare's storage system. We may consider adding this back in the future.

M

MrBBot•6/30/23, 12:45 PM

If you need access to production data, you're best bet for now is to use

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote.

W

Walshy•7/1/23, 8:28 PM

Vitest and unstable dev is still the way

V

vassbence•7/1/23, 10:07 PM

How does the team feel currently about the --local, --preview and the --env flags? They can get quite messy

V

vassbence•7/1/23, 10:07 PM

KV doesnt work with --local, what does --preview do if I can use --env staging --env production etc

V

vassbence•7/1/23, 10:07 PM

I'd love to see a bit of streamlining

Vvassbence KV doesnt work with --local, what does --preview do if I can use --env staging -...

H

Hello, I’m Allie!•7/1/23, 10:08 PM

What version of

wrangler

wrangler

are you running?

H

Hello, I’m Allie!•7/1/23, 10:09 PM

Because

wrangler preview

wrangler preview

wrangler preview

wrangler preview is still a thing in the latest version of

wrangler

wrangler

, but there isn't a

--preview

--preview

--preview

--preview flag.

H

Hello, I’m Allie!•7/1/23, 10:09 PM

And KV should work fine locally. It won't pull values from production KV, but it should still work

V

vassbence•7/1/23, 10:09 PM

wrangler dev using KV saves to local sqlite

V

vassbence•7/1/23, 10:10 PM

and I cant put into this same local sqlite KV with wrangler kv

V

vassbence•7/1/23, 10:10 PM

it just goes to the preview KV which is online

V

vassbence•7/1/23, 10:12 PM

(already reported on github)

B

bkyerv•7/2/23, 10:02 AM

I'm finding myself uncertain about the optimal way to kick off a new project using Wrangler. Trying to utilize init leads to a deprecation warning and an advice to switch to cloudflare@2. Does this suggest that the wrangler CLI tool is being supplanted by the cloudflare@2 package? Additionally, when choosing react as the framework to develop a web project, create-react-app is the tool offered for building react-based projects. Is there any specific rationale behind not incorporating vite as an option or an alternative to create-react-app for constructing a React application? Does the team managing cloudflare@2 consider create-react-app as more appropriate for react-based applications compared to those built on vite?

Rroman Hi everyone! I'm developing with `wrangler dev` and found that I cannot securely...

H

Hello, I’m Allie!•7/2/23, 10:35 PM

You can generate the .dev.vars file before starting the dev session, if that is what you mean?

E

Erisa•7/3/23, 9:23 AM

https://developers.cloudflare.com/workers/wrangler/api/#unstable_dev

API · Cloudflare Workers docs

Wrangler offers an experimental API to programmatically manage your Cloudflare Workers.

V

Vero•7/3/23, 3:38 PM

Hey devs, @Wrangler office hours will start soon, join us to ask questions about Wrangler, Quick Edit, workerd, miniflare, etc.
https://discord.gg/cloudflaredev?event=1121506821874659478

N

Nick Randall•7/3/23, 5:54 PM

Does anybody know how to do instantiate a wasm module in a javascript worker? FWIW, the wasm was built with Rust + Wasm Pack.

N

Nick Randall•7/3/23, 5:54 PM

Yes, I know I can author a worker in rust, but I have a use case for using a small wasm module in a JS worker.

K

kian•7/3/23, 6:21 PM

Just your usual WebAssembly.instantiate API

N

Nick Randall•7/3/23, 6:23 PM

Importing a

.wasm

.wasm

.wasm

.wasm module seems to just return an empty ES Module not bytes or a

WebAssembly.Module

WebAssembly.Module

WebAssembly.Module

WebAssembly.Module object that

WebAssembly.instantiate

WebAssembly.instantiate

WebAssembly.instantiate

WebAssembly.instantiate is expecting

N

Nick Randall•7/3/23, 6:24 PM

How do I get the Module and/or raw bytes for the module?

K

kian•7/3/23, 6:24 PM

How are you importing it?

K

kian•7/3/23, 6:52 PM

For local development, those are the only choices.

N

Nick Randall•7/3/23, 6:53 PM

import wasm from './module.wasm';
const instance = await WebAssembly.instantiate(wasm, {});

import wasm from './module.wasm';
const instance = await WebAssembly.instantiate(wasm, {});

import wasm from './module.wasm';
const instance = await WebAssembly.instantiate(wasm, {});

import wasm from './module.wasm';
const instance = await WebAssembly.instantiate(wasm, {});

NNick Randall ``` import wasm from './module.wasm'; const instance = await WebAssembly.instant...

K

kian•7/3/23, 6:57 PM

I can't replicate any issues with this code personally

N

Nick Randall•7/3/23, 7:00 PM

I'm still debugging but I think what I'm realizing that that the Worker API for wasm is not the same as what is documented by MDN.

is there a way to inherit all environment variables when using `wrangler dev` - currently finding th

Similar Threads

Similar Threads

Similar Threads