I'm running my worker locally with `yarn wrangler dev --node-compat` however I still get the error t

I'm running my worker locally with

yarn wrangler dev --node-compat

yarn wrangler dev --node-compat

yarn wrangler dev --node-compat

yarn wrangler dev --node-compat however I still get the error there are no matching exports even though they should be supported according to the docs (https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/)

✘ [ERROR] No matching export in "node-modules-polyfills:crypto" for import "randomBytes"

    src/index.ts:38:9:
      38 │ import { randomBytes } from 'node:crypto';
         ╵          ~~~~~~~~~~~

✘ [ERROR] No matching export in "node-modules-polyfills:crypto" for import "randomBytes"

    src/index.ts:38:9:
      38 │ import { randomBytes } from 'node:crypto';
         ╵          ~~~~~~~~~~~

✘ [ERROR] No matching export in "node-modules-polyfills:crypto" for import "randomBytes"

    src/index.ts:38:9:
      38 │ import { randomBytes } from 'node:crypto';
         ╵          ~~~~~~~~~~~

✘ [ERROR] No matching export in "node-modules-polyfills:crypto" for import "randomBytes"

    src/index.ts:38:9:
      38 │ import { randomBytes } from 'node:crypto';
         ╵          ~~~~~~~~~~~

Am I doing something wrong here?

Arma•1/17/24, 4:32 PM

I had a similar issue with crypto.randomUUID()crypto.randomUUID()

Arma•1/17/24, 4:32 PM

import crypto from 'node:crypto';import crypto from 'node:crypto'; does not work

Arma•1/17/24, 4:33 PM

There is a default crypto.randomUUID()crypto.randomUUID() and crypto.getRandomValues()crypto.getRandomValues() in the Worker runtime, I ended up using that even though it may not be 100% node compatible

DDenni I'm running my worker locally with `yarn wrangler dev --node-compat` however I s...

Hello, I’m Allie!•1/17/24, 4:34 PM

Did you enable the

nodejs_compat

nodejs_compat

flag?

Hello, I’m Allie!•1/17/24, 4:35 PM

What you are showing is --node-compat--node-compat, which is the old polyfill method

Hello, I’m Allie!•1/17/24, 4:35 PM

It has support for less stuff

Hello, I’m Allie!•1/17/24, 4:37 PM

HHello, I’m Allie!Did you enable the `nodejs_compat` flag?

DenniOP•1/17/24, 4:39 PM

That fixes my example code but I'm working with a third party library which no longer works when using

nodejs_compat

nodejs_compat

because it imports cryptocrypto instead of node:cryptonode:crypto. Is there some way I can make this third party library use the polyfill modules?

DDenni That fixes my example code but I'm working with a third party library which no l...

Hello, I’m Allie!•1/17/24, 4:40 PM

Maybe an

esbuild

esbuild

alias? https://esbuild.github.io/api/#alias

esbuild - API

Hello, I’m Allie!•1/17/24, 4:41 PM

Rename cryptocrypto to node:cryptonode:crypto, then mark it as external

DenniOP•1/17/24, 4:41 PM

That might work, but it seems a little weird to me that this is the best way to do it when --node-compat--node-compat worked out of the box. Is this really the way to go when using any third party library that uses node modules?

DDenni That might work, but it seems a little weird to me that this is the best way to ...

Hello, I’m Allie!•1/17/24, 4:42 PM

Maybe? I generally just avoid deps that require Node, but I know that isn't feasible for everyone

Hello, I’m Allie!•1/17/24, 4:42 PM

Don't remember the exact reasoning for it, but iirc it was something about Node's APIs not being JS-standard, so they wanted to scope them

Hello, I’m Allie!•1/17/24, 4:43 PM

Just like how non-standard Cloudflare APIs that require an import are scoped cloudflare:cloudflare:

kian•1/17/24, 4:44 PM

Given there’s 4,521 dependents on the “crypto” lib on npm (which is built into Node now, yes) still meowlul

kian•1/17/24, 4:46 PM

TIL they literally nuked it other than a deprecation README

kian•1/17/24, 4:47 PM

Anyways, there was work in Wrangler to make it automatically turn crypto -> node:crypto (and others) for you but that isn't done yet

HHello, I’m Allie!Maybe an `esbuild` alias? https://esbuild.github.io/api/#alias

DenniOP•1/17/24, 4:50 PM

How do I supply arguments like this to esbuild through wrangler?

DenniOP•1/17/24, 4:50 PM

I'm not very familiar with TS build tools at all

DDenni How do I supply arguments like this to esbuild through wrangler?

Hello, I’m Allie!•1/17/24, 4:55 PM

You have to install

esbuild

esbuild

, then run the build yourself

Hello, I’m Allie!•1/17/24, 4:55 PM

There are like 3 things you can configure on esbuild when using the wranglerwrangler provided one

HHello, I’m Allie!You have to install `esbuild`, then run the build yourself

DenniOP•1/17/24, 4:59 PM

That sounds like it would need a lot of config to get it to work with cloudflare

DenniOP•1/17/24, 5:01 PM

It seems the library I'm using does have a browser version you can build yourself. I'll look into how to integrate that

Advany•1/17/24, 5:10 PM

anyone else not able to deploy? sees like wangler login isn't working. Gate way error 504

DDenni It seems the library I'm using _does_ have a browser version you can build yours...

DenniOP•1/17/24, 5:13 PM

Okay, this doesn't quite seem to work either. Is it possible it's trying to access browser APIs that CF Workers don't have access to?

DenniOP•1/17/24, 5:14 PM

I'm not getting any build errors this time, it just doesn't work and throws warnings and tries to reconnect

kian•1/17/24, 5:15 PM

What package are you trying to use?

DenniOP•1/17/24, 5:17 PM

I'm using gramjs, a Telegram client. It has both a node and browser version

DenniOP•1/17/24, 5:17 PM

CF Workers might not be the best way to do this but I need something to automatically send a couple of telegram messages once per day

AAdvany anyone else not able to deploy? sees like wangler login isn't working. Gate way ...

Advany•1/17/24, 5:26 PM

working again

Deo Kumar•1/17/24, 8:15 PM

Does wasm binaries bundled using wrangler deploywrangler deploy count in 1MB limit?
Because my worker.js size is 940KiB and overall size including wasm is 2.3MiB after bundling but it throws the error workers.api.error.script_too_largeworkers.api.error.script_too_large

kian•1/17/24, 8:27 PM

Yes

Advany•1/17/24, 9:48 PM

mhhh... if I am doing wrangler dev (and I dont do await on a htmlrewrite transform), it doesnt work. But it works deployed when doing return rewriter.transform(response);

Advany•1/17/24, 9:50 PM

I should just do await then right?

Advany•1/17/24, 9:51 PM

In the docs there is no await so thats why I was confused!

kian•1/17/24, 9:54 PM

You can return a Promise from an async function (i.e the

fetch

fetch

handler) without awaiting it

Advany•1/17/24, 10:11 PM

yeah, I do that... but seems like when using locally (so without --remote) the htmlrewriter isn't running. Le tme create a sample project to show it

AA•1/18/24, 1:52 AM

need to find a nice way to create apis that can be consumed by workers. openapi seems so heavy these days.. tho maybe hono makes it nice

AA•1/18/24, 1:57 AM

using stuff like zodios/trpc and messing around with mono repos also an option i guess

Bob•1/18/24, 11:49 AM

I'm having a hard time grasping the worker concept of environment variables. I'm using hono and I want to create a variable outside hono 'c.env' context. I don't understand Where this 'env' comes from.

Bob•1/18/24, 11:53 AM

for example: app.use('/input/*', bearerAuth({ TOKEN }));app.use('/input/*', bearerAuth({ TOKEN })); I would normally use 'process.env.TOKEN'

BBob for example: `app.use('/input/*', bearerAuth({ TOKEN }));` I would normally use ...

Hello, I’m Allie!•1/18/24, 12:02 PM

You would do something like

app.use('/input/*', (c, next) => bearerAuth({ c.env.TOKEN })(c, next));

app.use('/input/*', (c, next) => bearerAuth({ c.env.TOKEN })(c, next));

HHello, I’m Allie!You would do something like ```ts app.use('/input/*', (c, next) => bearerAuth({ ...

Bob•1/18/24, 12:04 PM

My hero! What it I just want to access them outside of the "app." context?

BBob My hero! What it I just want to access them outside of the "app." context?

Hello, I’m Allie!•1/18/24, 12:04 PM

Like, in the global scope? Is this for initializing a client or something?

Bob•1/18/24, 12:04 PM

yes

BBob yes

Hello, I’m Allie!•1/18/24, 12:04 PM

Then you would initialize it within the appapp scope, then store it in a global

Hello, I’m Allie!•1/18/24, 12:05 PM

You could also use an AsyncLocalStorage to have it accessible globally(but that requires a compat flag)

Hello, I’m Allie!•1/18/24, 12:05 PM

But note, env vars are only ever available in the context of handling an incoming event

Hello, I’m Allie!•1/18/24, 12:05 PM

For example, you can't just pull a secret on startup

I'm running my worker locally with `yarn wrangler dev --node-compat` however I still get the error t

Similar Threads

Similar Threads

Similar Threads