Murder Chicken
05/21/2023, 5:26 PMrequests
is an array of Request objects)...
const responseData = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
... no longer works resulting in this error...
Cannot read properties of undefined (reading 'map')
TypeError: Cannot read properties of undefined (reading 'forEach')
Which has me baffled... trying to figure out where it's failing.Skye
05/21/2023, 5:27 PMMurder Chicken
05/21/2023, 5:28 PMMurder Chicken
05/21/2023, 5:34 PMexport async function example() {
const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
let data = responses.map(response => processResponse(response['records']))
let records = data.flat(3)
records.forEach(a => {
// Failure is this forEach
})
}
Murder Chicken
05/21/2023, 5:36 PMMurder Chicken
05/21/2023, 5:37 PMMurder Chicken
05/21/2023, 5:38 PMSkye
05/21/2023, 5:38 PMMurder Chicken
05/21/2023, 5:40 PMMurder Chicken
05/21/2023, 6:28 PMscheduledEvent
from a development environment similar to the --test-scheduled
flag and hitting the __scheduled
route locally?James
05/21/2023, 6:36 PM/cdn-cgi/mf/scheduled
but I don't believe that's a thing anymore with v3 unfortunately.Dani Foldi
05/21/2023, 6:38 PMMurder Chicken
05/21/2023, 7:02 PM--test-scheduled
flag and hit the __scheduled
route at the root of the domain. but once it's pushed to a development environment in CF, you have to wait for the event to trigger so I was hoping we could somehow trigger it manually.stan
05/21/2023, 8:06 PMstan
05/21/2023, 8:07 PMJames
05/21/2023, 8:07 PMsilence
05/21/2023, 10:49 PMnpx wrangler pages dev...
if it was a workers function i would put usage_model="unbound"
in my wrangler.tomltobytraylor
05/22/2023, 12:38 AMidv
05/22/2023, 3:51 AMwj
05/22/2023, 3:55 AMMatt
05/22/2023, 5:01 AMAlaanor
05/22/2023, 9:02 AMIsaac McFadyen | YYZ01
05/22/2023, 11:55 AMMmaZik
05/22/2023, 12:26 PMundefined
. Anyone can help? I have no idea why it can't see each other when running locally.
This is my env during dev, for Workers A (caller):
[env.dev]
vars = { ENVIRONMENT = "dev", ENV = "dev" }
services = [
{ binding = "SERVICES", service = "workers-services", environment = "dev" }
]
And this is for Workers B (being called):
[env.dev]
name = "workers-services"
vars = { ENVIRONMENT = "dev", ENV = "dev" }
When I run with --remote
(using Wrangler v3.0.0), I get this error: **text: 'workers.api.error.service_binding_env_error: could not resolve binding "SERVICES":
environment "dev" not found for service "workers-services" [code: 10144]'**
These are however separate project, one is Bundled (A) and one is Unbound (B). One is nodejs compat (B), one is not (A).MmaZik
05/22/2023, 12:28 PM--remote
, it spits out the error message just a short time after starting. When running locally (which is the default since wrangler v3.0.0 I assume), the env.SERVICE
is undefined. Running live, no problem.banbanboi
05/22/2023, 1:34 PMsathoro
05/22/2023, 2:34 PMbanbanboi
05/22/2023, 2:45 PMBenParr
05/22/2023, 2:59 PM