Workers support the Web Crypto standard by default, if I recall correctly the screenshot is from the

Workers support the Web Crypto standard by default, if I recall correctly the screenshot is from the nodejs compat crypto, which does support createHmac and you can enable it in your worker.
You'll need to add

compatibility_flags = ['nodejs_compat']

compatibility_flags = ['nodejs_compat']

compatibility_flags = ['nodejs_compat']

compatibility_flags = ['nodejs_compat'] to your wrangler.toml (if you have other flags, append

nodejs_compat

nodejs_compat

) to enable it, then you will be able to use it like this:

import { createHmac } from 'node:crypto'

function somewhereInYourCode() {
  createHmac('sha256', 'secret')
}

import { createHmac } from 'node:crypto'

function somewhereInYourCode() {
  createHmac('sha256', 'secret')
}

import { createHmac } from 'node:crypto'

function somewhereInYourCode() {
  createHmac('sha256', 'secret')
}

import { createHmac } from 'node:crypto'

function somewhereInYourCode() {
  createHmac('sha256', 'secret')
}

DDaniFoldi Workers support the Web Crypto standard by default, if I recall correctly the sc...

leeo•12/6/23, 9:53 AM

thanks , but compatibility_flags = ['nodejs_compat'] give me an error.

Lleeo thanks , but compatibility_flags = ['nodejs_compat'] give me an error.

DaniFoldiOP•12/6/23, 9:54 AM

could you share the error?

leeo•12/6/23, 9:54 AM

✘ [ERROR] The

nodejs_compat

nodejs_compat

compatibility flag cannot be used in conjunction with the legacy --node-compat--node-compat flag. If you want to use the Workers runtime Node.js compatibility features, please remove the --node-compat--node-compat argument from your CLI command or node_compat = truenode_compat = true from your config file.

DaniFoldiOP•12/6/23, 9:55 AM

right, so you're using the legacy polyfills, as well as trying to use the new compatibility mode, is there anything that you need the old polyfills for?

leeo•12/6/23, 9:55 AM

No, how i can fix this error

leeo•12/6/23, 9:56 AM

I got this i just remove the node_compat = truenode_compat = true and it works now. thanks.

Lleeo I got this i just remove the `node_compat = true` and it works now. thanks.

DaniFoldiOP•12/6/23, 9:57 AM

yep, that is the solution, glad it works MeowHeartCloudflare

leeo•12/6/23, 10:11 AM

another question, i want to use ffmpeg-wasm in wokers, ffmpeg-wasm support webworker for now. Looking forward to workers supporting ffmpeg-wasm, so that I can do some audio and video processing. Now I have to deploy another docker to accomplish this.

dave•12/6/23, 4:42 PM

Is there an easy way to share Worker scripts for non-technical ish people to install on their account?

Ddave Is there an easy way to share Worker scripts for non-technical ish people to ins...

Hello, I’m Allie!•12/6/23, 4:47 PM

Worker scripts?

HHello, I’m Allie!Worker scripts?

dave•12/6/23, 5:06 PM

sorry, Worker scripts. Was multitasking too much here.

James•12/6/23, 8:24 PM

What happens if you place it into cache with a cache-control: no-transformcache-control: no-transform header?

Hearse•12/6/23, 9:48 PM

I am using hono, i have a database with a list of users and their credentials, is there any way i can setup auth and restrict specific routes for those users. I only need to do login

Pato•12/7/23, 1:32 AM

Hey! Has anyone here experimented with or implemented a system on Cloudflare Workers where you can dynamically instantiate or create workers from a template, particularly for a SaaS-like business model?

PPato Hey! Has anyone here experimented with or implemented a system on Cloudflare Wor...

Unsmart•12/7/23, 2:02 AM

Sounds like you want #workers-for-platforms

UUnsmart Sounds like you want #workers-for-platforms

Pato•12/7/23, 2:17 AM

Okay okay, do you know of an example i could check?

Unsmart•12/7/23, 2:18 AM

Should be a repo pinned that has example usage

dave•12/7/23, 4:05 AM

Is there any easy recommended way to make a script that can be run as a node CLI tool, or as a Worker?

Original message was deleted

dave•12/7/23, 4:37 PM

ah right, node will ignore the default exported fetch?

FoUnDeR•12/7/23, 4:39 PM

what kind of stuff I can do with cf workers?

Unsmart•12/7/23, 4:42 PM

a lot

UUnsmart a lot

FoUnDeR•12/7/23, 5:12 PM

thats pretty interesting

Deleted User 7f983ae1•12/7/23, 5:18 PM

Are there anyway to make the worker return a response first

Deleted User 7f983ae1•12/7/23, 5:18 PM

then do some KV/D1 operation

Deleted User 7f983ae1•12/7/23, 5:19 PM

after the request being send to the user

DDeleted User 7f983ae1 after the request being send to the user

Unsmart•12/7/23, 5:20 PM

https://developers.cloudflare.com/workers/runtime-apis/handlers/fetch/#contextwaituntil

Fetch Handler · Cloudflare Workers docs

Incoming HTTP requests to a Worker are passed to the fetch() handler as a request object. To respond to the request with a response, return a Response …

Deleted User 7f983ae1•12/7/23, 5:22 PM

so I just replace await with context.waitUntil(

Deleted User 7f983ae1•12/7/23, 5:23 PM

also 1 issue is I am making a counter

Deleted User 7f983ae1•12/7/23, 5:23 PM

so it also require to fetch from KV

Unsmart•12/7/23, 5:24 PM

If you want it to be perfectly accurate you should not do it in a waitUntil because waitUntil can fail or stop running and you wouldve responded that it suceeded

Deleted User 7f983ae1•12/7/23, 5:24 PM

I don't need it to be perfectly accurate

Deleted User 7f983ae1•12/7/23, 5:24 PM

just some general statistic

Deleted User 7f983ae1•12/7/23, 5:25 PM

Just counter also require read operation and then write so idk how to add it

Deleted User 7f983ae1•12/7/23, 5:25 PM

create a new async function?

Unsmart•12/7/23, 5:26 PM

You can do anything you want inside of wait until. But also KV for a counter is not a good idea. KV generally only allows 1 write per second per key.

Deleted User 7f983ae1•12/7/23, 5:27 PM