getting `crypto.pbkdf2Sync is not a function` when using https://www.npmjs.com/package/cryptr on wor

getting

crypto.pbkdf2Sync is not a function

crypto.pbkdf2Sync is not a function

when using https://www.npmjs.com/package/cryptr on workers

npm

cryptr

a simple encrypt and decrypt module for node.js. Latest version: 6.3.0, last published: 3 months ago. Start using cryptr in your project by running

npm i cryptr

npm i cryptr

. There are 309 other projects in the npm registry using cryptr.

bunOP•12/13/23, 11:43 AM

not sure how to fix it

Bbun getting `crypto.pbkdf2Sync is not a function` when using https://www.npmjs.com/p...

Erisa•12/13/23, 11:50 AM

Based on the code and that error I suspect its trying to use Node.js crypto, which in Workers requires the

nodejs_compat

nodejs_compat

compatability flag https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/ but also probably still wont work without a modification to the library because it

require

require

crypto

crypto

instead of

node:crypto

node:crypto

But once those two hurdles are surpassed,

pbkdf2Sync

pbkdf2Sync

is listed as supported in our implementattion of Node.js crypto

bunOP•12/13/23, 11:51 AM

bunOP•12/13/23, 11:51 AM

so change

const crypto = require('crypto');

const crypto = require('crypto');

import crypto from "node:crypto"

import crypto from "node:crypto"

Erisa•12/13/23, 11:52 AM

Something like that yeah, sounds about right

Erisa•12/13/23, 11:52 AM

It also uses Buffer so you might need to do something for that if its mandatory https://developers.cloudflare.com/workers/runtime-apis/nodejs/buffer/

bunOP•12/13/23, 11:52 AM

noted

Erisa•12/13/23, 11:53 AM

And the compatibility flag to unlock the

node:

node:

stuff is just

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

in your wrangler.toml

bunOP•12/13/23, 11:53 AM

oh i didthis

bunOP•12/13/23, 11:53 AM

thats what the error message said to use

Erisa•12/13/23, 11:54 AM

The error message lies

bunOP•12/13/23, 11:54 AM

Erisa•12/13/23, 11:54 AM

node_compat = true

node_compat = true

is the old implementation

Erisa•12/13/23, 11:55 AM

methinks the error message needs to be updated, I should check if theres an existing issue on workers-sdk

bunOP•12/13/23, 11:55 AM

rip i dont think

createDecipheriv

createDecipheriv

works

Erisa•12/13/23, 11:55 AM

Bogdan•12/13/23, 3:45 PM

i think i might have posted in the wrong channel: wranglerWebsocket using correctly

Bogdan•12/13/23, 3:45 PM

some help would be appreciated

rusty•12/13/23, 6:22 PM

Is there a way to deploy javascript module as worker via API? I am trying:

$ curl --request PUT \
        --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \
        --header 'Authorization: Bearer {token_id}' \
        --header 'Content-Type: application/javascript' \
        --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

$ curl --request PUT \
        --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \
        --header 'Authorization: Bearer {token_id}' \
        --header 'Content-Type: application/javascript' \
        --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

But getting error:

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "workers.api.error.content_type"
    }
  ],
  "messages": []
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "workers.api.error.content_type"
    }
  ],
  "messages": []
}

When I deploy using

wrangler

wrangler

, there is no problem. Is there a dedicated header for mjs?

kian•12/13/23, 6:23 PM

https://developers.cloudflare.com/api/operations/worker-script-upload-worker-module

kian•12/13/23, 6:23 PM

Change the body to

multipart/form-data

multipart/form-data

and follow that documentation.

kian•12/13/23, 6:23 PM

rusty•12/13/23, 6:24 PM

thank you! Will try

kian•12/13/23, 6:25 PM

You could also refer to how Wrangler does it: https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/src/deployment-bundle/create-worker-upload-form.ts

Alexey Ch.•12/13/23, 8:09 PM

Hello! Has anyone encountered such a problem that Real-time Logs do not work? Moreover, for none of my Workers, including those that I haven’t touched for a long time. When I try to start I get the following message: "Could not establish websocket connection. Begin log stream to try again."

AA•12/13/23, 8:17 PM

huh. today is a new compatibility date? 2023-12-13

AA•12/13/23, 8:19 PM

doesnt list the changes

kian•12/13/23, 8:21 PM

Compatibility dates can be any date as long as it isn't in the future. The last date to have a specific change seems to be

2023-12-01

2023-12-01

which is

crypto_preserve_public_exponent

crypto_preserve_public_exponent

AA•12/13/23, 8:24 PM

ah ok

AA•12/13/23, 8:25 PM

for some reason i thought it always jumped to the last change

Chaika•12/13/23, 8:41 PM

for a bit Miniflare/wrangler dev used to get upset and warn if you set your compat date ahead of a current one but that was silenced now

Chaika•12/13/23, 8:43 PM

It would log
"[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-05-25". Falling back to "2023-05-18"..."
maybe that's where you got that from?

lukas•12/13/23, 10:49 PM

Curious, I am trying to save a new Response in a new Map for memory cache, and after I retrieve the value by cache key from the new Map, and I use the .json method on it, I get this error (only happening in worker code, not in a regular nodejs app

i was getting errors like this

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

lukas•12/13/23, 10:49 PM

Why is that?

kian•12/13/23, 11:10 PM

Just a limitation of Workers like the error says.

Anil•12/14/23, 9:39 AM

is there a documentation about pricing, i did a small POC project, after a day it says "Billable duration 1.72k GB-sec" is this something that i need to care ?

V1NUM•12/14/23, 9:45 AM

I have a worker right now that just displays a maintenance page. How do i make it as simple as possible to just set all traffic to that maintenance mode when i want to?

Mitya•12/14/23, 10:38 AM

Asked this in #workers-help but didn't get an answer yet. Wonder if someone can help. Is it possible to specify different Hyperdrives for different environments in TOML? e.g. the live env specifies Hyperdrive A and the stage env specifies Hyperdrive B.

MMitya Asked this in #workers-help but didn't get an answer yet. Wonder if someone can ...

Erisa•12/14/23, 10:42 AM

For Hyperdrive questions I recommend asking in #hyperdrive-beta where the team is active, individual teams for products don't always monitor channels like this or #workers-help

EErisa For Hyperdrive questions I recommend asking in #hyperdrive-beta where the team i...

Mitya•12/14/23, 11:50 AM

Aha sorry - I asked here because I figured it was more of a Wrangler/TOML question, but will ask in Hyperdrive.

EErisa And the compatibility flag to unlock the `node:` stuff is just ```toml compatibi...

bunOP•12/14/23, 12:55 PM

deploying another worker, this didn't work smide

bunOP•12/14/23, 12:56 PM

returned the same node_compat error, only fixed when i put

node_compat = true

node_compat = true

kian•12/14/23, 12:56 PM

nodejs_compat

nodejs_compat

only covers a subset of modules and they must be imported with the

node:

node:

prefix -

node_compat

node_compat

is a set of polyfills added at build-time which covers a lot more modules.

bunOP•12/14/23, 12:56 PM

bunOP•12/14/23, 12:56 PM

bit confusing KEKW

kian•12/14/23, 12:58 PM

nodejs_compat

nodejs_compat

is a new-ish push towards providing NodeJS built-ins at runtime whereas

node_compat

node_compat

is fairly old - once

nodejs_compat

nodejs_compat

provides enough coverage to remove the need for

node_compat

node_compat

then

node_compat

node_compat

would be removed.

kian•12/14/23, 12:59 PM

One of the big issues w/

nodejs_compat

nodejs_compat

is the requirement of a

node:

node:

prefix when importing the module, but there is work to have Wrangler handle that automatically for you.

Antonio32A•12/14/23, 1:56 PM

What's the maximum duration a TCP socket can be kept alive? 30s?

sathoro•12/14/23, 2:04 PM

just started getting this all of a sudden for a particular domain when calling

fetch

fetch

. I've got internet, am able to access it in my browser, have restarted the dev server, reset my internet, etc

only seems to be one particular domain

$ curl --request PUT \ --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \ --header 'Authorization: Bearer {token_id}' \ --header 'Content-Type: application/javascript' \ --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

getting `crypto.pbkdf2Sync is not a function` when using https://www.npmjs.com/package/cryptr on wor

Similar Threads

Similar Threads

Similar Threads