-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
What version of Wrangler are you using?
0.0.25
What operating system are you using?
Mac
Describe the Bug
When using uppercase characters for the script name in wrangler.toml, e.g. name = "Test", wrangler throws a "ParseError: Received a bad response from the API" when running npx wrangler dev.
Steps to Reproduce
➜ npx wrangler@beta init
⛅️ wrangler 0.0.25
--------------------
…
Would you like to create a Worker at src/index.ts? (y/n)
✨ Created src/index.ts
index.ts
export default {
async fetch(request: Request): Promise<Response> {
return new Response("Hello World!");
},
};
wrangler.toml
name = "Test"
main = "src/index.ts"
compatibility_date = "2022-04-14"
Terminal output
➜ npx wrangler dev
⛅️ wrangler 0.0.25
--------------------
Select an account from below:
❯ 25thhour
⬣ Listening at http://localhost:8787
remote worker: ParseError: Received a bad response from the API
at throwFetchError (/Users/jdeane/dev/demos/vidAEo/node_modules/wrangler/wrangler-dist/cli.js:137650:17)
at fetchResult (/Users/jdeane/dev/demos/vidAEo/node_modules/wrangler/wrangler-dist/cli.js:137623:5)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async createPreviewToken (/Users/jdeane/dev/demos/vidAEo/node_modules/wrangler/wrangler-dist/cli.js:139904:29)
at async createWorkerPreview (/Users/jdeane/dev/demos/vidAEo/node_modules/wrangler/wrangler-dist/cli.js:139919:17)
at async start (/Users/jdeane/dev/demos/vidAEo/node_modules/wrangler/wrangler-dist/cli.js:140357:16) {
text: 'Received a bad response from the API',
notes: [ { text: 'workers.api.error.invalid_script_name [code: 10016]' } ],
location: undefined,
kind: 'error',
code: 10016
}
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels