Tymoteusz Czech

Right. Even `resolvedValue.value | ` is not strictly correct. Only way I know to make this work is to switch to [Intersection Types](https://www.typescriptlang.org/docs/handbook/unions-and-intersections.html#intersection-types), but that will export `type` instead of...

I narrowed the problem down to [`packages/apollo-language-server/src/workspace.ts#L117`](https://github.com/apollographql/apollo-tooling/blob/62f8beba53d57079a51e2d8a7af1167d39b85847/packages/apollo-language-server/src/workspace.ts#L117) PR welcome? I would try to substitute `glob` package with `fast-glob`, since it looks like this was the intent behind `fg` variable.

This can be done with Animation Tweaks extension. https://extensions.gnome.org/extension/1680/animation-tweaks/

Getting at least the dimensions/ratio is very useful for static site generators. There already is a way to get this information from headers if `IMGPROXY_ENABLE_DEBUG_HEADERS` is on. The `imagemeta` package...

Merged in https://github.com/Unleash/unleash-proxy-client-js/pull/224

# What we have right now ## Server-side ### App Router You can do it with App Router server-side fetch cache, example here: https://github.com/Unleash/unleash-client-nextjs/blob/main/example/src/app/app-page/page.tsx#L22 ```ts const definitions = await getDefinitions({...

# Plans ### Client-side I'll add an example of how to implement API route "proxying" for frontend API.

You can use caching on SSR. [(docs)](https://nextjs.org/docs/pages/building-your-application/data-fetching/get-server-side-props#caching-with-server-side-rendering-ssr). Downside is that if you are returning definitions from there to the client, you will expose your configuration. You can filter toggles you're...

I don't think that will run as expected on Cloudflare/Vercel etc. I'll experiment with it later this week. And again, if you have any user-land implementations, sharing it will help...

Ok. Thank you for explaining 👍🏻 I'm in favor of wrapping `cache(getDefinitions(...), ttl)` in a functional style instead of OOP instances. It's flexible. An example use case with long-running Next.js...