Cloudflare

Or just `if(!proto_res?.properties?.periods)` with optional chaining

are you 100% certain that API is perfect and only ever returns JSON when asked? 😅  When working with external APIs, it's always better to add resilience by checking what's actually returned

if .properties dont exist shouldn't .properties.periods be undefined?
and if it is, i do check that
```ts
export function exists<T>(data: T|null|undefined): data is T {
  if (
      (data === null) ||
      (data === undefined)
  ) return false;
  return true;
}
```

`.properties.periods` would throw a `TypeError` if `properties` doesn't exist. For example:
```js
const obj = {foo: 'bar'}
console.log(obj.foo) // bar
console.log(obj.bar) // undefined
console.log(obj.bar.baz) // TypeError
```

I want to create a single git repo, with lots of workers (mostly webhooks, so stripe/ses/etc)  this seems smarter than 1 big project since i can update/change them 1 at a time..  anyone have a good example of how to structure this? just 1 directory per worker, with its own wrangler? or?

right right 😅
https://cdn.discordapp.com/attachments/779390076219686943/1112098934026932244/Screenshot_2023-05-28_at_12.53.54_AM.png

`  (error) Error: Unexpected Server Error` lol I sure wish this error was better

since `performance.now()` isn’t available in Workers and `Date.now()` doesn’t increment unless you do I/O is there any way to actually benchmark CPU bound function execution times in a worker?

`performance.now()` is available but it just calls `Date.now()`

That’s annoying. Other platforms mitigate timing attacks but just skewing the resolution, but outright disabling it is an approach i guess

wrangler tail <-- all i get are OKs even tho I'm generating `internal server error`  anyplace to look to see better logging?

```ts
import { Hono } from 'hono'
import { Client } from 'pg'

const app = new Hono()

const connstring = "postgresql://postgres@localhost:5432/hhscdev?schema=public"

app.get('*', async (c) => {
  const client = new Client("postgresql://postgres@localhost:5432/hhscdev?schema=public");
  await client.connect();
  
  const { rows: [{ now }] } = await client.query('select now();');
  return c.text(`Hello Hono! ${now}`)
})

export default app
```

yeah Hono does it's own catching of unknown errors

So that's why it's ok, the error is being handled

you can do `app.onError` to add your own handler

ah, just using that because its recommended.  wonder if i should abandon it. or find a way to dump the error

really just using a single 'url' per project, so maybe hono is overkill

<@453920106498621451> thanks. 1 problem down. 99 more to go 🙂

ooh, another minor quirk. i'm doing a wrangler --env staging..  but in the workers dashboard it says the environment is 'production'  are these things not linked?

also did a vars = { ENVIRONMENT = "staging" }