was just reading up on traditional streams vs web streams in node. I may be wrong but I wonder if yo

M

mattOP•7/1/23, 8:50 AM

Am I doing this wrong? I picked it up rom bindings.spec.ts

mounts: {
  books: {
    // here I define name, scriptPath, modules, compatDate, compatFlags, bindings
  } 
}

mounts: {
  books: {
    // here I define name, scriptPath, modules, compatDate, compatFlags, bindings
  } 
}

mounts: {
  books: {
    // here I define name, scriptPath, modules, compatDate, compatFlags, bindings
  } 
}

mounts: {
  books: {
    // here I define name, scriptPath, modules, compatDate, compatFlags, bindings
  } 
}

Worker "core:user:example"'s binding "BOOKS" refers to a service "core:user:books", but no such service is defined

Worker "core:user:example"'s binding "BOOKS" refers to a service "core:user:books", but no such service is defined

Worker "core:user:example"'s binding "BOOKS" refers to a service "core:user:books", but no such service is defined

Worker "core:user:example"'s binding "BOOKS" refers to a service "core:user:books", but no such service is defined

M

mattOP•7/1/23, 8:53 AM

for now I am getting away with ... its working but I worry about the overhead

serviceBindings.books = req => {
  const smf = new Miniflare(<same options as mount config>)
  return smf.dispatchFetch(req)  
}

serviceBindings.books = req => {
  const smf = new Miniflare(<same options as mount config>)
  return smf.dispatchFetch(req)  
}

serviceBindings.books = req => {
  const smf = new Miniflare(<same options as mount config>)
  return smf.dispatchFetch(req)  
}

serviceBindings.books = req => {
  const smf = new Miniflare(<same options as mount config>)
  return smf.dispatchFetch(req)  
}

Mmatt was just reading up on traditional streams vs web streams in node. I may be wron...

M

MrBBot•7/1/23, 8:53 AM

Yep, that should work in modern Node versions. Miniflare’s minimum supported version is 16.13.0, which doesn’t provide those web stream adapters.

M

mattOP•7/1/23, 8:54 AM

that's a very good point, I always forget about the older versions of node

Mmatt Am I doing this wrong? I picked it up rom bindings.spec.ts ``` mounts: { books...

M

MrBBot•7/1/23, 8:55 AM

Miniflare 3 doesn’t use mounts anymore, checkout the migration guide for a multi-worker example: https://miniflare.dev/get-started/migrating#removed-options

⬆️ Migrating from Version 2 · Miniflare

Fun, full-featured, fully-local simulator for Cloudflare Workers

M

mattOP•7/1/23, 8:56 AM

this is brilliant, thank you

T

TravisFrank•7/3/23, 10:14 AM

@mrbbot Any idea what's going on here? Will keep digging

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Socket.Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/nexus/node_modules/miniflare/src/runtime/index.ts:132:26)
    at async Miniflare.#assembleAndUpdateConfig (/nexus/node_modules/miniflare/src/index.ts:790:23)
    at async Miniflare.#init (/nexus/node_modules/miniflare/src/index.ts:472:5) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Socket.Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/nexus/node_modules/miniflare/src/runtime/index.ts:132:26)
    at async Miniflare.#assembleAndUpdateConfig (/nexus/node_modules/miniflare/src/index.ts:790:23)
    at async Miniflare.#init (/nexus/node_modules/miniflare/src/index.ts:472:5) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Socket.Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/nexus/node_modules/miniflare/src/runtime/index.ts:132:26)
    at async Miniflare.#assembleAndUpdateConfig (/nexus/node_modules/miniflare/src/index.ts:790:23)
    at async Miniflare.#init (/nexus/node_modules/miniflare/src/index.ts:472:5) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Socket.Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/nexus/node_modules/miniflare/src/runtime/index.ts:132:26)
    at async Miniflare.#assembleAndUpdateConfig (/nexus/node_modules/miniflare/src/index.ts:790:23)
    at async Miniflare.#init (/nexus/node_modules/miniflare/src/index.ts:472:5) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

M

mattOP•7/4/23, 6:38 AM

hi again

I'm getting this error

workerd/jsg/util.c++:276: error: e = kj/compat/tls.c++:215: failed: TLS peer's certificate is not trusted; reason = unable to get local issuer certificate

workerd/jsg/util.c++:276: error: e = kj/compat/tls.c++:215: failed: TLS peer's certificate is not trusted; reason = unable to get local issuer certificate

workerd/jsg/util.c++:276: error: e = kj/compat/tls.c++:215: failed: TLS peer's certificate is not trusted; reason = unable to get local issuer certificate

workerd/jsg/util.c++:276: error: e = kj/compat/tls.c++:215: failed: TLS peer's certificate is not trusted; reason = unable to get local issuer certificate

it only appears when I use service bindings like this:

serviceBindings[bindingName] = req => {
  const smf = new Miniflare(options)
  return smf.dispatchFetch(req)
}

serviceBindings[bindingName] = req => {
  const smf = new Miniflare(options)
  return smf.dispatchFetch(req)
}

serviceBindings[bindingName] = req => {
  const smf = new Miniflare(options)
  return smf.dispatchFetch(req)
}

serviceBindings[bindingName] = req => {
  const smf = new Miniflare(options)
  return smf.dispatchFetch(req)
}

T

Tin Cap•7/7/23, 10:30 PM

I'm trying to understand the future of Miniflare. It sounds like the v3 integrated into Wrangler is going to have substantially less functionality than v2. Is that correct?

WWallslide I've noticed that if I have a DO alarm setup, and I make a change to the DO's co...

M

MrBBot•7/10/23, 10:52 AM

Hey!

Yep, this is correct. Alarms are currently on persisted between script reloads. If you need to test your alarm code, you'll want to shorten your timeouts.

TTin Cap I'm trying to understand the future of Miniflare. It sounds like the v3 integrat...

M

MrBBot•7/10/23, 11:00 AM

Miniflare is still it's own product, with an API you can use directly (https://github.com/cloudflare/miniflare/blob/tre/packages/miniflare/README.md), but Wrangler is the primary consumer of that API. The big change with Miniflare v3 is that we're using the same

workerd

workerd

runtime as deployed on Cloudflare's network to run your code, instead of reimplementing workers runtime APIs in Node.js. This significantly increases the fidelity of local mode. However, because we're now running your code in a separate process, some of Miniflare v2's features that relied on passing JavaScript references from inside the workers sandbox to other Node.js code are now much more difficult to implement. Namely, the Jest/Vitest testing environments and the

Miniflare#get*()

Miniflare#get*()

Miniflare#get*()

Miniflare#get*() methods. We're actively working on bringing the testing environments back, and are planning to add back deprecated support for

getBindings()

getBindings()

getBindings()

getBindings()/

getKVNamespace()

getKVNamespace()

getKVNamespace()

getKVNamespace()/

getR2Bucket()

getR2Bucket()

getR2Bucket()

getR2Bucket()/

getCaches()

getCaches()

getCaches()

getCaches()/

getDurableObjectNamespace()

getDurableObjectNamespace()

getDurableObjectNamespace()

getDurableObjectNamespace() whilst we figure out a better way to support framework dev servers. https://github.com/cloudflare/miniflare/discussions/588 has some more discussion around this.

RRaindrops When using the Miniflare for testing I get this error on version 3.20230628.0 I...

M

MrBBot•7/10/23, 11:04 AM

Miniflare no longer autoloads configuration from

wrangler.toml

wrangler.toml

. That responsibility has been delgated to Wrangler's

unstable_dev()

unstable_dev()

unstable_dev()

unstable_dev() API (https://developers.cloudflare.com/workers/wrangler/api/#unstable_dev). We're working on stabilising this at the moment, and the API is likely to change significantly in the future. For now, I'd recommend translating your

wrangler.toml

wrangler.toml

to Miniflare API options (https://github.com/cloudflare/miniflare/blob/tre/packages/miniflare/README.md). To fix the specific error you're seeing, you'll likely need to add

modules: true

modules: true

modules: true

modules: true, but you may also need to configure

kvNamespaces

kvNamespaces

kvNamespaces

kvNamespaces/

r2Buckets

r2Buckets

r2Buckets

r2Buckets/etc if you're using those.

RRaindrops Thank you so much! It kinda worked, cause now I am getting a new error

M

MrBBot•7/10/23, 3:20 PM

Hmmm, are there any other logs above this?

K

katopz•7/11/23, 8:41 AM

weird

npx miniflare

npx miniflare

npx miniflare

npx miniflare fail on my mac ( via

devDependencies

devDependencies

also not working)

36 verbose stack Error: could not determine executable to run
36 verbose stack     at getBinFromManifest (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/get-bin-from-manifest.js:17:23)
36 verbose stack     at exec (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:185:15)
36 verbose stack     at async module.exports (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/lib/cli.js:134:5)
37 verbose pkgid miniflare@3.20230628.0

36 verbose stack Error: could not determine executable to run
36 verbose stack     at getBinFromManifest (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/get-bin-from-manifest.js:17:23)
36 verbose stack     at exec (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:185:15)
36 verbose stack     at async module.exports (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/lib/cli.js:134:5)
37 verbose pkgid miniflare@3.20230628.0

36 verbose stack Error: could not determine executable to run
36 verbose stack     at getBinFromManifest (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/get-bin-from-manifest.js:17:23)
36 verbose stack     at exec (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:185:15)
36 verbose stack     at async module.exports (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/lib/cli.js:134:5)
37 verbose pkgid miniflare@3.20230628.0

36 verbose stack Error: could not determine executable to run
36 verbose stack     at getBinFromManifest (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/get-bin-from-manifest.js:17:23)
36 verbose stack     at exec (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:185:15)
36 verbose stack     at async module.exports (/Users/katopz/.nvm/versions/node/v18.16.0/lib/node_modules/npm/lib/cli.js:134:5)
37 verbose pkgid miniflare@3.20230628.0

and

yarn

yarn

also fail, not thing work on my machine. maybe only me

K

katopz•7/11/23, 9:47 AM

oh not only me and this pretty confusing https://community.cloudflare.com/t/help-with-miniflare-cli-on-mac/515217

Kkatopz oh not only me and this pretty confusing https://community.cloudflare.com/t/hel...

H

Hello, I’m Allie!•7/11/23, 1:42 PM

Basically, with Miniflare 3 and up, all local development now happens through Wrangler, rather than Miniflare

HHello, I’m Allie!Basically, with Miniflare 3 and up, all local development now happens through Wr...

K

katopz•7/11/23, 1:46 PM

yeah, i just realized that. a lot of tuts and examples still use

miniflare

miniflare

even here https://github.com/cloudflare/miniflare#using-the-cli so it would be nicer to mention there too.

GitHub

GitHub - cloudflare/miniflare: 🔥 Fully-local simulator for Cloudfla...

Fully-local simulator for Cloudflare Workers. Contribute to cloudflare/miniflare development by creating an account on GitHub.

GitHub - cloudflare/miniflare: 🔥 Fully-local simulator for Cloudfla...

Kkoudelka Is there an recommended way to use typescript with miniflare 3? I think for now ...

M

MrBBot•7/15/23, 8:36 AM

Correct, Miniflare only supports JavaScript. You could use

wrangler dev

wrangler dev

though, which will compile your TypeScript for you before passing it to Miniflare.

T

Tony Leung•7/15/23, 1:44 PM

hi guys, is there any easy way to run fullstack sveltekit locally with hot reload enabled? To make hot reload works, I have to run

wrangler pages dev .svelte-kit/cloudflare --local

wrangler pages dev .svelte-kit/cloudflare --local

wrangler pages dev .svelte-kit/cloudflare --local

wrangler pages dev .svelte-kit/cloudflare --local then run

npm run build

npm run build

everytime I make a change, which is not convenient

TTony Leung hi guys, is there any easy way to run fullstack sveltekit locally with hot reloa...

K

katopz•7/16/23, 2:27 AM

i use

npx nodemon -e ts,tsx,css -w ./ --ignore dist --exec npm run build

npx nodemon -e ts,tsx,css -w ./ --ignore dist --exec npm run build

npx nodemon -e ts,tsx,css -w ./ --ignore dist --exec npm run build

npx nodemon -e ts,tsx,css -w ./ --ignore dist --exec npm run build as workaround.

D

DeChill•7/16/23, 1:30 PM

Hi

Am I right in assuming that Miniflare 2 has no support for the DO WebSockets Hibernation API?

J

James•7/16/23, 3:27 PM

As far as I know, that is correct, yes

D

DeChill•7/16/23, 3:38 PM

Ah, that's a bummer

Unfortunately I'm unable to update to V3 due to the breaking changes in the bindings API. I'm using Miniflare programatically from a (CF Pages) SvelteKit app which needs the bindings to be available for the Vite dev server (https://github.com/cloudflare/miniflare/discussions/588#discussioncomment-5996494).

I guess I'll fork the V2 repo and try to add some rudimentary support for the hibernation API...

Kkatopz i use `npx nodemon -e ts,tsx,css -w ./ --ignore dist --exec npm run build` as wo...

T

Tony Leung•7/16/23, 4:13 PM

is there anyway to make svelte build a non-minify/uglify worker code so I can easily debug? Now I'm using the old method: Placing a lot of

console.log

console.log

to identify the error part of the code. Sorry I'm not a TS/JS veteran.

TTony Leung is there anyway to make svelte build a non-minify/uglify worker code so I can ea...

K

katopz•7/16/23, 4:17 PM

i know nothing about

svelte

svelte

svelte

svelte sorry

T

Tony Leung•7/16/23, 4:18 PM

okay thanks, I think I can deal with it

MMrBBot Miniflare is still it's own product, with an API you can use directly (<https://...

D

DeChill•7/17/23, 9:35 AM

Regarding the future of MF3: We're really looking forward to a (very rough) timeline for some of the missing features in Miniflare V3.

And by that I don't mean exact dates, but rather trying to understand if it's Weeks, Months, or Years away and how much effort we should put into forking/extending Miniflare V2 since as you mentioned, the

getBindings()

getBindings()

getBindings()

getBindings() APIs are crucial for testing and framework dev servers.

DDeChill Regarding the future of MF3: We're really looking forward to a (very rough) time...

M

MrBBot•7/17/23, 10:31 AM

Hey!

From that discussion:
- Step-through debugging: ~1 month
- Trigger scheduled events via CRON schedules: ~1 month
- HTTPS servers: done!
- Unit testing environments: ~3 months
-

getBindings()

getBindings()

getBindings()

getBindings()/

getKVNamespace()

getKVNamespace()

getKVNamespace()

getKVNamespace()/

getR2Bucket()

getR2Bucket()

getR2Bucket()

getR2Bucket()/

getCaches()

getCaches()

getCaches()

getCaches()/

getDurableObjectNamespace()

getDurableObjectNamespace()

getDurableObjectNamespace()

getDurableObjectNamespace(): ~1 month
-

getGlobalScope()

getGlobalScope()

getGlobalScope()

getGlobalScope()/

getModuleExports()

getModuleExports()

getModuleExports()

getModuleExports(): probably not coming back

K

kian•7/17/23, 4:18 PM

Would https://github.com/cloudflare/workerd/pull/867 allow

globalThis.MINIFLARE

globalThis.MINIFLARE

globalThis.MINIFLARE

globalThis.MINIFLARE to make a return?

GitHub

wip: context bootstrap modules by mikea · Pull Request #867 · cloud...

Kkian Would https://github.com/cloudflare/workerd/pull/867 allow `globalThis.MINIFLARE...

M

MrBBot•7/17/23, 9:35 PM

Hmmm, maybe, will have to play with it once it's merged

MMrBBot Hey! 👋 From that discussion: - Step-through debugging: ~1 month - Trigger sched...

S

Shirokawa•7/25/23, 5:15 AM

Just found this update through a link in the workers discussion channel. Thanks a lot!
Can I ask, what does "Unit testing environments" entail?
The main trouble I currently have with wrangler/workers is difficulty in writing proper tests.

SShirokawa Just found this update through a link in the workers discussion channel. Thanks ...

M

MrBBot•7/25/23, 7:22 AM

Bringing https://miniflare.dev/testing/vitest to Miniflare 3

MMrBBot Bringing <https://miniflare.dev/testing/vitest> to Miniflare 3

S

Shirokawa•7/28/23, 2:33 AM

Thanks a lot for the clarification! Looking forward to that very much as that's exactly what we need.

Is there an issue, PR or something where one could follow the development?

SShirokawa Thanks a lot for the clarification! Looking forward to that very much as that's ...

M

MrBBot•7/28/23, 6:46 AM

Not yet unfortunately, we’re still thinking about how it’s going to work

MMrBBot Not yet unfortunately, we’re still thinking about how it’s going to work 👍

S

Shirokawa•7/28/23, 6:47 AM

Ok! Thanks a lot!:)

B

Bram•8/2/23, 8:43 AM

Hi, considering miniflare 3 does not work (yet) with vitest, is it fine to stay with miniflare 2?

A

Adi•8/3/23, 3:11 AM

Looks like vitest version

0.34.1

0.34.1

0.34.1

0.34.1 surfaced an interesting bug in

vitest-environment-miniflare

vitest-environment-miniflare

vitest-environment-miniflare

vitest-environment-miniflare. Made an issue for it - https://github.com/cloudflare/miniflare/issues/645

GitHub

[Bug] vitest-environment-miniflare breaks when using vitest 0.34.1 ...

Package versions vitest: 0.34.1 vitest-environment-miniflare: 2.14.0 NOTE: I know for a fact that everything was working correctly with vitest 0.33.0. The issue surfaced just in the latest release....

BBram Hi, considering miniflare 3 does not work (yet) with vitest, is it fine to stay ...

M

MrBBot•8/3/23, 7:22 AM

Hey!

Yep, if you need the unit testing environments, I’d stick with v2 for the time being.

AAdi Looks like vitest version `0.34.1` surfaced an interesting bug in `vitest-enviro...

M

MrBBot•8/3/23, 7:24 AM

Thanks for reporting this, will try fix it soon.

V

valkyrie_pilot•8/9/23, 7:42 PM

Is there a way to access a miniflare r2 bucket locally as if it's a public bucket?

K

kian•8/9/23, 7:46 PM

Nope, there's no local public or S3 API emulation.

Kkian Nope, there's no local public or S3 API emulation.

F

fs0x30•8/9/23, 9:02 PM

similar question, how would one access a emulated r2 upload locally then? I'm not using S3 just r2 storage

S

sathoro•8/14/23, 4:42 PM

through the binding the same as remote

was just reading up on traditional streams vs web streams in node. I may be wrong but I wonder if yo

Similar Threads

Similar Threads

Similar Threads