Erik Wittern

[Erik Wittern @erikwittern]

@dan_abramov @vercel @Netlify @Azure @Cloudflare @AWSAmplify @Firebase Here is an example configuration for @Firebase Hosting to serve a statically exported Next.js SPA with multiple HTML entries, including dynamic routes (e.g., /products/[productId]): https://t.co/mWw60GFZmg

[Erik Wittern @erikwittern]

@Firebase @puf Very cool to see `OR` queries!

They allow, for example, to improve prefix string matches to be (slightly less) case-sensitive (cf. https://t.co/o1GCWNHXmc).

[Erik Wittern @erikwittern]

It's a PWA, so it can be added to home screens and be used like an app. It's also client-side only. Topics are reflected in the URL and additionally persisted to local storage.

[Erik Wittern @erikwittern]

I wrote a small HN client, for fun.
You can "subscribe to" topics ("React", "TypeScript", "ChatGPT" or similar) and view the most relevant posts & discussions for different time frames (1 day, 7 days etc.)
https://t.co/F3BwGNoc1C

[Erik Wittern @erikwittern]

@mbleigh I imagine such a feature fits very well with Firestore’s architecture, and is mostly a matter of making information on this level available via SDKs?!

[Erik Wittern @erikwittern]

@mbleigh For example, it would make it much easier to implement collaborative forms where in the client one wants to update (re-render) only form inputs whose value just changed.

[Erik Wittern @erikwittern]

Rewrites, in our case, are done for Firebase hosting. It’s not automatic, but easy enough to maintain.

[Erik Wittern @erikwittern]

This is exactly how we build https://t.co/TtLbvwBV9m. The experience is great. Our app is highly interactive, so the SPA model fits well, and hosting is cheap. However, we still benefit from build-time-rendered HTML files + JS chunks, allowing e.g. our blog to be SEO-friendly.

[Erik Wittern @erikwittern]

@bechtweets @dvassallo Ah, thanks for the explanation.

[Erik Wittern @erikwittern]

@dvassallo @bechtweets $10/m with 2M paid subscribers should mean around 240M per year in revenue, no?

[Erik Wittern @erikwittern]

If you want to rely on URL query parameters in React components in a reactive way, useSyncExternalStore makes it pretty simple when combined with a proxy object.

https://t.co/BFVfZtbT3c

[Erik Wittern @erikwittern]

It's the holiday season. Time to draft wish lists. In this case, for some amazing features that would oh-so-much improve the jolly #firebase services.

https://t.co/nNB4oKtshE

[Erik Wittern @erikwittern]

I wrote about how we combine @Firebase Firestore 🔥 with Zustand in Coup's React app. Our setup allows components to subscribe to updates of individual documents, even though we use a single Firestore query to listen to changes across multiple documents.

https://t.co/P7EjFn1Ph5

[Erik Wittern @erikwittern]

When building an API, how to choose between REST, GraphQL, or RPC frameworks? Certain requirements can really drive the decision.

Here is my (current) take:

https://t.co/8sb7ShYNAx

[Erik Wittern @erikwittern]

@__xuorig__ Fully agree. The benefit is that cost analysis adds latency, so having to run it only once when “deploying” is a huge improvement over running it on every request.

[Erik Wittern @erikwittern]

@Firebase Very interested in the new `firebase deploy` functionality for Next.js. Does it support server-side rendering (i.e., does it setup a Cloud Function running the Next.js server for that)? Or is it merely about deploying a site previously built statically (using `next export`)?

[Erik Wittern @erikwittern]

@mbleigh - No more Cloud Function cold start performance issues when using (Firestore) gRPC SDKs (cf. https://t.co/ixrhswuqRz)
- More configuration options for Auth Email Action Links (specifically, configurable expiration times)
- Seamless hosting of Next.js apps (cf. Vercel or Netlify)

[Erik Wittern @erikwittern]

@mxstbr @GraphCDN This is awesome! If I‘d still be doing research I‘d jump on this.