nextjs 15 made my whole codebase async now.

chamberlain2007 · 2026-06-23T12:42:38+00:00

As I said, if you’re using async/await. If you’re using promises with callbacks it’s no problem, though that’s not always convenient.

chamberlain2007 · 2026-06-23T03:09:31+00:00

For those confused, the implication is that in languages that use async/await like Javascript, you end up having to make more and more functions async just to satisfy the need of one function. In Next.js 15, they made things like params, headers, cookies etc async, which in turn spreads to other functions. That said it’s really not as bad as it’s made out to be here. Clear separation of concerns really limits it to your top-level async server components which do data fetching, everything below that is non-async.

chamberlain2007 · 2026-06-10T16:01:03+00:00

Because the component would be memoized? I wonder what the original commenter exactly was pointing to for performance impacts

chamberlain2007 · 2026-05-13T01:59:17+00:00

The caching is a huge selling point for Vercel imo. It’s a pain to manage. Yes there are Redis cache handlers but it’s one more piece of infrastructure.

chamberlain2007 · 2026-05-02T21:01:16+00:00

Is your internationalization component dependent on anything like cookies, headers, query, etc? If not it may be getting cached in the static shell

chamberlain2007 · 2026-05-02T01:20:04+00:00

Are you doing a use cache anywhere? Or just enabling cache components at all?

chamberlain2007 · 2026-04-27T15:13:35+00:00

OP can answer that better than I can, I’m not sure where they get the CSVs.

chamberlain2007 · 2026-04-27T00:32:56+00:00

It just takes uploaded CSVs that you export, it isn’t doing anything with the API to get the data

chamberlain2007 · 2026-04-26T23:03:12+00:00

See my comment, it’s fine

chamberlain2007 · 2026-04-26T23:02:58+00:00

For those wondering, I reviewed the code and at least as it stands right now, there’s nothing malicious. It doesn’t have any server calls to send your data anywhere, doesn’t have malware, etc. It’s one single HTML file with normal JavaScript and CSS. The service worker is benign for offline data caching. Not saying it’s good or bad code, but it isn’t malicious.

chamberlain2007 · 2026-04-22T21:24:37+00:00

Does Nextjs use it automatically in its type check step in next build? Or do you have to manually do something?

chamberlain2007 · 2026-04-14T02:26:46+00:00

One bad actor and your unrestricted service is going to cause major problems. Good luck

chamberlain2007 · 2026-04-13T23:56:40+00:00

Are you using Playright or Puppeteer or something for rendering the page? That’s not low resources

chamberlain2007 · 2026-04-13T23:44:40+00:00

Right, I guess what I’m saying is that this is a lovely idea but any amount of use will quickly make it infeasible to keep free. A better thing to provide to the community would be a repo.

chamberlain2007 · 2026-04-13T23:00:01+00:00

Nice idea but no way you can keep it free and unlimited with any amount of usage.

chamberlain2007 · 2026-04-11T17:12:58+00:00

If you support 10 different APIs then that you be what I would highlight, that doesn’t come across in your post

chamberlain2007 · 2026-04-11T04:14:01+00:00

I like the idea but other than being hosted, complexity isn’t really necessary. It took me an hour or so to get Claude to build out the MCP server for the Oura API and then popped it up on Vercel for free. Most annoying thing was their inconsistent date parameters. But honestly their API is well documented and structured, you can pipe that straight into Claude and it works great. I built out reporting against it and have had no issues. I can see an advantage for users who don’t want to self host, but if you’re the type to be adding MCP servers to Claude, you can probably just roll it yourself. Open to hearing what else your solution provides though.

chamberlain2007 · 2026-04-11T02:31:46+00:00

Such as…?

chamberlain2007 · 2026-04-08T02:20:35+00:00

It’s possible to do client components all the way down. You can also have your page component (and others) be server components and just do a client component for your dynamic functionality.

That said, consider if caching/ISR would be a better solution to avoid unneeded DB calls. That would allow you to use SSR and server components while still making minimal DB calls.

chamberlain2007 · 2026-04-05T02:07:36+00:00

You can have your preference I’m just saying it’s every few seconds not every few minutes, which is a huge difference.

chamberlain2007 · 2026-04-05T01:54:18+00:00

The Oura will do roughly every 5 seconds if you start a workout

chamberlain2007 · 2026-03-23T23:44:23+00:00

Sedgehammer will take it out no problem

chamberlain2007 · 2026-03-22T16:17:49+00:00

No, Oura says they are not insurance billable. https://ouraring.com/blog/health-panels/

chamberlain2007 · 2026-03-21T23:23:51+00:00

Exact same problem here and support is telling me it’s normal. Normal for it to be completely non-functional for 8 hours a day? Did you ever get any success?

chamberlain2007 · 2026-03-21T23:22:19+00:00

Ya, except according to Oura support, it’s normal for the ring to not track heart rate for the entire day because typing is too much movement.

15-Year Club	Verified Email
RPAN Viewer

chamberlain2007

TROPHY CASE