John Schulz

I ran into this yesterday and @KianNH helped me in the Cloudflare Discord. A worker fetches data from an API running on AWS. I changed the API from one address...

wrangler now logs a warning as of https://github.com/cloudflare/wrangler2/pull/992

Based on https://github.com/cloudflare/wrangler2/issues/975#issuecomment-1169126913 this is a bug that will be fixed and is tracked in https://github.com/cloudflare/wrangler2/issues/1320

@Leonidas-from-XIV how do you feel about adding `parseStringSync` which returns the result?

Is anyone currently working on this? @michaelficarra?

Let me know if I'm missed something and it is possible today. I'm happy to help, especially if you've already got an idea of how/where to do it. It seems...

> The thing is, the props for each page comes from user-land since you can basically return anything you need from the props handler (that's why the data property is...

Also, if we define the routes a bit differently diff showing individual routes with unique `name` and `path` ```diff diff --git a/examples/react/src/routes.js b/examples/react/src/routes.js index 81695be..d98e813 100644 --- a/examples/react/src/routes.js +++ b/examples/react/src/routes.js...

I hadn't thought about the virtual entry (I'm new to vite/vue/etc and they're new to me) but that seems really interesting. In used them in https://github.com/jfsiii/reactesse-use-deep-props/blob/5f8420c6828ef2502dac362e299d211aaa8793e3/vite.config.ts#L49 toI stash the original...

I'm not sure how far we can get to knowing _exactly_ what type are on what page/props/api, but I would like to start with getting types for pages, like there...