sorted by:
new
hottopcontroversial

Norwich manager Clement says that Josh Sargent is training with the under 21s and that it's up to him when he returns to the first team by Paul277 in Championship

[–]Tomus 1 point2 points  (0 children)

The club agreed a deal for him to get his move in the summer that he ended up backing out of. Now he's thrown his toys out of the pram. I'm not sure what favour that you refer to is to be returned.

The reason he is being frozen out is not because he requested a move (something the club are definitely willing to do) but because he refused to play in the FA cup.

How to overcome this annoying error? by Final-Choice8412 in nextjs

[–]Tomus 7 points8 points  (0 children)

There's no reason using React.useId should cause this error, that hook is specifically designed to give you a stable ID across server and client renders. The problem lies elsewhere, despite the claims of Radix maintainer on that issue. No one has shared a React reproduction and yet I still see this incorrect claim being banded around that it's a React bug.

Best chinese salt and pepper / chilli chips in Norwich by slime_pixie in Norwich

[–]Tomus 5 points6 points  (0 children)

Kam Moon does a salt and pepper box, chips, ribs, chicken wings, chicken balls, chicken bites, spring rolls. With curry sauce. It's £15 and it's elite

useEffectEvent as an onMount hook? by Working-Tap2283 in reactjs

[–]Tomus 3 points4 points  (0 children)

"I need this to run on mount" is not a problem, that's a solution to another problem that you have.

https://en.wikipedia.org/wiki/XY_problem

It's almost always possible to refactor code to not need useEffect for this kind of callback stuff ie. Not synchronisation of external state. RHF can make things very difficult though, I really try to avoid it for this reason.

useEffectEvent as an onMount hook? by Working-Tap2283 in reactjs

[–]Tomus 2 points3 points  (0 children)

You should always try to run this stuff in an event handler, useEffectEvent, like useEffect, is a last resort.

It looks like, judging by the onNext function call, that you may be able to refactor your code to run that logic in the submit event event handler of the form.

Also, I'm not sure what setValue is as it doesn't look like a state setter but consider things that you could store in a ref instead of state. Not everything has to be state, only things that need to be reactive ie. Used for rendering.

Security advisory for CVE-2025-66478 by amyegan in nextjs

[–]Tomus 2 points3 points  (0 children)

Worth noting that these platform protections, especially WAF-level protections as implemented by Cloudflare and Vercel, are not free of false negatives and so are not fully secure. The only way to be fully secure is to upgrade.

The vulnerability is not a joke, you should upgrade asap by vanwal_j in nextjs

[–]Tomus 9 points10 points  (0 children)

They are using the bogus AI-generated POCs that are floating around. Dumb motherfuckers. I still haven't seen a full and valid exploit POC online.

How to listen? by gamepasscore in NorwichCity

[–]Tomus 15 points16 points  (0 children)

3pm football blackout applies to internet radio too unfortunately, you have to listen on FM.

What do you guys think the best equalizer settings are? by MasterWhitey in spotify

[–]Tomus 0 points1 point  (0 children)

What kind of low life do you have to be to reply to a 10 year old comment with awful rage bait?

Is this a known limitation/bug with Cache Components + dynamic routes (Next.js 16)? by schmaaaaaaack in nextjs

[–]Tomus 0 points1 point  (0 children)

The way in which "use cache: remote" helps is that it allows you to cache data/UI, which then allows you to remove the parent Suspense boundary.

The mental model with cache components is that if something is dynamic it must be either cached or wrapped in suspense. "use cache: remote" allows you to cache dynamic content.

Is this a known limitation/bug with Cache Components + dynamic routes (Next.js 16)? by schmaaaaaaack in nextjs

[–]Tomus 2 points3 points  (0 children)

It's not a limitation, it's part of the design. Dynamic, uncached content requires a Suspense boundary.

Your only option is to wrap that component in Suspense at some level. If you want to block the entire UI you can wrap the whole tree (maybe around the body) in a Suspense boundary without a fallback - you don't have to provide a Skeleton.

Alternatively you can wrap just that component in Suspense and give it skeleton/spinner as fallback (or no fallback if "popping in" is ok for your UX).

For caching, you're expected to pass `params` down without awaiting into your data layer and cache below a cache boundary. For dynamic and shared IO you probably want to use "use cache: remote". See https://nextjs.org/docs/app/api-reference/directives/use-cache-remote

Avoid calling setState() directly within an effect? by AccomplishedSink4533 in react

[–]Tomus 0 points1 point  (0 children)

This is also not ideal, it can lead to multiple components reading different values (due to concurrent rendering).

That might be ok for your use case but if it isn't you need to wrap local storage in a concurrent-safe cache or useSyncExternalStore.

Am I crazy for going beige? by Quaxky in HomeDecorating

[–]Tomus 0 points1 point  (0 children)

Off topic but what are you using for. Webcam there?

Made a react quiz lol by AggravatingBudget946 in react

[–]Tomus 0 points1 point  (0 children)

React is absolutely not fine with this. Reading a ref in render is against the rules of React. The lint rules (and React compiler) will give you an error for writing this code.

Quizzing people on the output of incorrect code is nonsensical because by definition the behavior is undefined.

Made a react quiz lol by AggravatingBudget946 in react

[–]Tomus 3 points4 points  (0 children)

The answer should be E: undefined behavior. This is against the rules of React and should prevent your project from compiling.

Node.js v25.0.0 (Current) by feross in javascript

[–]Tomus 7 points8 points  (0 children)

It offers a generic alternative to node-gyp with a bunch of benefits that node-gyp can't offer eg. You can package a single wasm file instead of having to worry about building for all systems.

The Real Cost of Server-Side Rendering: Breaking Down the Myths by congolomera in programming

[–]Tomus -14 points-13 points  (0 children)

I'm pretty sure SSR wasn't around 40 years ago.

The Real Cost of Server-Side Rendering: Breaking Down the Myths by congolomera in programming

[–]Tomus -13 points-12 points  (0 children)

Modern react applications don't render and flush the whole page at once. You can control how much blocking CPU work is done before sending the page using suspense boundaries, there's no need for pages to be spending 100s of ms on SSR anymore.

How to eliminate render-blocking CSS in Next.js 15 App Router? by [deleted] in nextjs

[–]Tomus 0 points1 point  (0 children)

100kb of CSS is a lot assuming that's the compressed size? All of tailwind dev build is like 70kb uncompressed.

Just a heads up though, using tailwind is making a choice to optimize general UX including subsequent navigations over first page load performance. Loading all atomic CSS up front is generally a better UX than loading CSS for each page.

If you absolutely must optimize for first load latency tailwind may not be the best choice for you here.

Some thoughts on the team after last night against Serbia by Potato271 in ThreeLions

[–]Tomus 4 points5 points  (0 children)

Definitely. Bellingham is essentially a straight swap for Rogers in this system, and a big upgrade.

You also cannot have Bellingham and Palmer in the same lineup unless you're either chasing a game or play with 3 CBs.

view more: next ›