{
"$schema": "node_modules/wrangler/config-schema.json"
}
H
KKKK
E
TKTT
K
G
A
C
A
https://localhost:5001/api/files/vault/bf09a8c8-54b3-4fb9-9d32-3a5e9d837ecb.jpeg in postman with auth header it works correctly. But when I do 8787 one in browser it doesn't And I see correct headers just before the call to inner fetch. Do you see if I am doing something wrong? Thank you.
E
N
N
KK
.vscode/settings.json
B
K
DHHHH
M
wrangler logincurl thing that's even more fragile because wrangler errors out before I could even curl the localhost url)MM
SUUSS
Mnpm run dev
MM
Lworkflow.yml and properly setup the secrets as attached but I get the error that the env variables are missing.npm run buildastro build or wrangler build for my workers with Hono) then wrangler pages deploy ./dist or wrangler deploy
L
Zwrangler kv bulk put? I tried following the docs, passing the following JSON:[
{
"key": "key1",
"value": "value1",
"metadata": "{ \"metadata1\": 1 }"
},
{
"key": "key2",
"value": "value2",
"metadata": "{ \"metadata2\": 2 }"
}
]⛅️ wrangler 3.99.0
-------------------
✘ [ERROR] Unexpected JSON input from "kv.json".
Each item in the array should be an object that matches:
interface KeyValue {
key: string;
value: string;
expiration?: number;
expiration_ttl?: number;
metadata?: object;
base64?: boolean;
}
The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}objectmetadata? In contrast, wrangler kv key put --metadata does accept a JSON-serialized string and works as expected.bulk put works as expected if I just pass the keyvalue, or with the example provided in the docs (passing an expiration_ttl).
Jhttps://localhost:5001/api/files/vault/bf09a8c8-54b3-4fb9-9d32-3a5e9d837ecb.jpeg[vars]
NODE_VERSION = "18.18.0" ~/IdeaProjects/workers-ms-render master !3 ?2 18:36:50
❯ npx wrangler dev
⛅️ wrangler 3.99.0
-------------------
Running custom build: cargo install -q worker-build && worker-build --release
╭──────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open devtools, [l] turn off local mode, [c] clear console, [x] to exit │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
[INFO]: 🎯 Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found in sysroot: "/opt/homebrew/Cellar/rust/1.83.0"
Used rustc from the following path: "/opt/homebrew/bin/rustc"
✘ [ERROR] Running custom build `cargo install -q worker-build && worker-build --release` failed. There are likely more logs from your build command above.
🪵 Logs were written to "/Users/alex/Library/Preferences/.wrangler/logs/wrangler-2024-12-23_17-37-02_261.log"curlbinding AI of type ai failed to generate: internal error; please try again later or contact
support [code: 10021]workflow.ymlastro buildwrangler buildwrangler pages deploy ./distwrangler kv bulk put[
{
"key": "key1",
"value": "value1",
"metadata": "{ \"metadata1\": 1 }"
},
{
"key": "key2",
"value": "value2",
"metadata": "{ \"metadata2\": 2 }"
}
]⛅️ wrangler 3.99.0
-------------------
✘ [ERROR] Unexpected JSON input from "kv.json".
Each item in the array should be an object that matches:
interface KeyValue {
key: string;
value: string;
expiration?: number;
expiration_ttl?: number;
metadata?: object;
base64?: boolean;
}
The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}metadatawrangler kv key put --metadatabulk putvalueexpiration_ttl[wrangler:err] Error: internal error
at async jsonError (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:10)
at async drainBody (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-ensure-req-body-drained.ts:5:10)export default {
async fetch(request, env, ctx) {
console.log('proxy intercept', request, env);
const url = new URL(request.url);
const host = env.VITE_BACKEND_HOST;
if (url.pathname.startsWith("/api")) {
// handle api
const pathname = url.pathname;
const search = url.search;
const pathWithParams = pathname + search;
const newUrl = `${host}${pathWithParams}`;
const cookies = parseAuthCookies(request.headers.get("cookie"), tabId);
const newRequest = new Request(request);
const token = cookies["Api.Token"];
if (token != null) {
newRequest.headers.set("Authorization", "Bearer " + token);
}
const response = await fetch(newUrl, newRequest); // exception
console.log("proxy response", response);
return response;
}
return fetch(url, request);
}
} "json.schemas": [
{
"fileMatch": ["wrangler.json"],
"url": "./node_modules/wrangler/config-schema.json"
}
],name: ⚡ Deploy to Cloudflare
on:
push:
branches:
- master
jobs:
deploy:
runs-on: ubuntu-latest
name: ☁️ Deploy
steps:
- name: 📥 Checkout
uses: actions/checkout@v3
- name: ⚙️ Use Node.js 18.x
uses: actions/setup-node@v1
with:
node-version: 18.x
- name: ⬇️ Install dependencies
run: npm install
- name: 🔨 Build apps & packages
run: npm run build
- name: 🚀 Deploy apps
run: npm run deploy
env:
CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}
CDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / general-helpCDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / workers-and-pages-help