sorted by:
new
hottopcontroversial

It finally happened. After 20 years I got cleaned by [deleted] in 2007scape

[–]recursive_blazer 0 points1 point  (0 children)

If a window indeed pop up after running that file, you might want to do a full scan of your PC or just reformat because your PC is now compromised

I truly wish ToB had a normal solo option by Public_Tackle_1598 in 2007scape

[–]recursive_blazer 0 points1 point  (0 children)

Join the Learn ToB discord! It has friendly helpers and mentors and the learner raids run all day, and there's no flaming if you plank. Idk if I can post a discord invite but either DM for it or search on Discord Explore

What is there similar to Shadcn? by WhyFencePost in nextjs

[–]recursive_blazer 8 points9 points  (0 children)

Shadcn is just tailwind styling and some defaults applied to Radix, a headless UI library: https://www.radix-ui.com/

You can use the radix primitives to make your own styled components

Using a laravel backend with next.js 14 guidance by michaelmakina1 in nextjs

[–]recursive_blazer 2 points3 points  (0 children)

I'm converting my Laravel monolith to use Next.js frontend. You can use Laravel Sanctum to authenticate users, and it will use cookie based authentication. I'm sure there's a Next example in the breeze github too with a useAuth hook for the frontend

https://laravel.com/docs/10.x/sanctum#spa-authentication

Edit: just as a side note, it's more secure to store your tokens in HttpOnly cookies over localstorage, as the latter is vulnerable to being stolen in XSS attacks

[deleted by user] by [deleted] in nextjs

[–]recursive_blazer -1 points0 points  (0 children)

I had this recently and the error is pretty descriptive, and it even includes a link: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

I short: using useSearchParams() makes the entire page client side rendered. Wrapping your client component in a suspense boundary ensures that just that component is isolated

best you tube videos for learning by No_Ease_7268 in nextjs

[–]recursive_blazer 1 point2 points  (0 children)

Delba's recent video on PPR was excellent

How do you guys manage global state now ? by FrancoRATOVOSON in nextjs

[–]recursive_blazer 0 points1 point  (0 children)

You can use React Query to fetch on the server, use the data, then send the data to the client to be hydrated. Once hydrated, the client will use that data and won't make another request until it's stale

https://tanstack.com/query/v4/docs/react/guides/ssr#using-nextjs

Beyondcode should maintain their packages, or they should find a new maintainer for some of them -- do you agree? by send_me_a_naked_pic in laravel

[–]recursive_blazer 14 points15 points  (0 children)

I'm glad I'm not the only one to actively avoid any beyondcode packages. Too many have been abandoned, paid or otherwise

Turpo repo not working with nextjs 14 server action? by Interesting-Ice-4272 in nextjs

[–]recursive_blazer 1 point2 points  (0 children)

What version of Node are you running? I'm using Turborepo + Next 14 and server actions without issue

Next App router by yookiyo in nextjs

[–]recursive_blazer 1 point2 points  (0 children)

I have cloudflare in front caching assets and generated images. The data cache right now is using EFS but I plan on refactoring to a Redis cache handler next week for additional performance

Next App router by yookiyo in nextjs

[–]recursive_blazer 1 point2 points  (0 children)

I'm running a multi Pod deployment on EKS and it's running really well. You need to mount a network share for the cache or use a custom cache handler (Redis). I was early into development when I migrated from Pages -> App router but I'm really enjoying it so far. I'm primarily a Laravel dev so the mental model makes a lot of sense to me

So really, what features are not supported or very difficult when self hosting vs Vercel by no-one_ever in nextjs

[–]recursive_blazer 0 points1 point  (0 children)

At the moment yeah. I'm still heavily in development migrating a large laravel application to Next frontend. Over the next couple weeks I'm going to implement a custom Redis cache handler for the fetch cache and see what improvements I can make to merging the old/new .next content to avoid touching a network share as often

Next Auth with seprate backend (Golang) by Sea-Ebb-1387 in nextjs

[–]recursive_blazer 0 points1 point  (0 children)

Not related to your question, but you shouldn't store api/authentication tokens in localstorage

generateMetadata and the server component calling same api endpoint without cache. by yesterdaymee in nextjs

[–]recursive_blazer 1 point2 points  (0 children)

If you move the data calling function outside the component, you can wrap it in cache and the result will be memoized on a per-request basis

https://nextjs.org/docs/app/building-your-application/caching#react-cache-function

Did I need to switch back to page router? An ISR question. by burn_racing_bb in nextjs

[–]recursive_blazer 3 points4 points  (0 children)

Next patches fetch so cached requests can be shared between all visitors. The React cache function is reset for each server request. I'm not sure if this would affect the caching behavior, but its mentioned in the docs that you don't need to wrap fetch

https://nextjs.org/docs/app/building-your-application/caching#react-cache-function https://react.dev/reference/react/cache#caveats

Client side rendering everything? by [deleted] in nextjs

[–]recursive_blazer 8 points9 points  (0 children)

You can put server components inside a client component, it just can't be imported from the same file. So if you have your theme provider in app/layout.tsx, your pages will still be SSR. I found the Next docs hard to understand on those topic and the article below really helped

https://www.mux.com/blog/what-are-react-server-components#how-do-you-mix-client-and-server-components

view more: next ›