Oh and computation is very little, its mainly my caching layer that I'm trying to optimize here
Oh and computation is very little, its mainly my caching layer that I'm trying to optimize here
colo on the east coast does not have the cache, it would retrieve it from another colo nearby that might have the cache, and if not, it would go to the origin?crypto.pbkdf2Sync is not a function when using https://www.npmjs.com/package/cryptr on workersnpm i cryptr. There are 309 other projects in the npm registry using cryptr.
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 requires crypto instead of node:cryptopbkdf2Syncis listed as supported in our implementattion of Node.js crypto
const crypto = require('crypto'); to import crypto from "node:crypto"?node: stuff is just in your wrangler.toml

node_compat = true is the old implementationcreateDecipheriv works
wrangler, there is no problem. Is there a dedicated header for mjs?multipart/form-data and follow that documentation.

2023-12-01 which is crypto_preserve_public_exponent
node_compat = true innodejs_compat only covers a subset of modules and they must be imported with the node: prefix - node_compat is a set of polyfills added at build-time which covers a lot more modules.colocolocrypto.pbkdf2Sync is not a functionnpm i cryptrcryptonode:cryptopbkdf2Syncconst crypto = require('crypto');import crypto from "node:crypto"node:node:node_compat = truenode_compat = truecreateDecipheriv$ 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") } }{
"result": null,
"success": false,
"errors": [
{
"code": 10001,
"message": "workers.api.error.content_type"
}
],
"messages": []
}multipart/form-data2023-12-01crypto_preserve_public_exponent<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.