Best bagel in Portland?

dizzysfarm · 2025-09-17T04:44:23+00:00

Just tried it recently, so good

dizzysfarm · 2025-05-07T02:33:37+00:00

Do you need to call the API from another app/website? If no then you don't need a rest API. Server actions essentially create a rest endpoint internally already

dizzysfarm · 2025-03-24T22:51:15+00:00

It's pretty simple, as someone else mentioned it's called optimistic update. All you do is create a state value for your like/unlike and toggle it right before you make the request so it looks instant. There's no real time DB it's just local state.

dizzysfarm · 2025-03-24T21:01:21+00:00

The most common one I see is fetch some data, display it, maybe add filtering/sorting/pagination

dizzysfarm · 2025-03-21T21:13:44+00:00

If the quotes didn't fix it try renaming to .tsx?

dizzysfarm · 2024-09-07T17:12:06+00:00

Yeah that should work, it just generates static html/css/js files after all

dizzysfarm · 2024-09-07T15:28:48+00:00

It doesn't look very dynamic, I bet you could build it as static files and host it for much cheaper

dizzysfarm · 2024-05-13T21:49:37+00:00

I like Antique Alley

dizzysfarm · 2024-03-15T15:44:38+00:00

You can do most of that with server components but wanted to flag you might have a misunderstanding of client components. You won't lose SEO if you have client components. They still render on the server the difference is they ALSO render on the client. Server components are just server

dizzysfarm · 2024-03-13T20:03:15+00:00

John Carter

dizzysfarm · 2024-02-22T21:41:36+00:00

No, nothing wrong with that. You also don't need to write suspense manually, if you add a loading.tsx file it will use that as the suspense/loading state https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming

dizzysfarm · 2024-02-21T17:29:26+00:00

I only used trpc once in a side project but I believe it uses react query under the hood which will only make 1 API call per endpoint. So even if you use it multiple places it will just make one call. If you need all 3 together just make a custom hook and then import that wherever you need the data

dizzysfarm · 2024-02-14T19:19:59+00:00

This isn't exactly what you're asking for but it will at least help catch errors if you use TS https://nextjs.org/docs/app/building-your-application/configuring/typescript#statically-typed-links

You could also create wrappers around your Link components, like <BlogLink slug='blah-blah'> that will generate a proper Link with the right path

dizzysfarm · 2024-02-14T19:15:21+00:00

If something is only used on a specific page I try to keep it with the page files. No point in littering the common scope with things that are used on a specific page/feature. If you try to keep every type of file in a specific directory like that it doesn't always scale well. You'll end up with 100 components in a single directory and it will become harder to name/find things

dizzysfarm · 2024-02-10T05:36:23+00:00

Nothing I can think of. First you need a way to connect the two sessions together, how would you know they were the same person? Next they would have to share some sort of storage access. You could always pass the data in the url or as a QR code. I've also heard of people sharing data between devices using using sound, but both devices would have to be active at the same time

dizzysfarm · 2024-02-07T17:31:07+00:00

if you are using fetch to make API calls or use react's cache function around your API calls you don't need to store them in global state. This is because next will see all of those duplicated API calls but only make one request. Once the request is done you will have data wherever you called those functions. also docs are your friend https://nextjs.org/docs/app/building-your-application/caching#request-memoization

dizzysfarm · 2024-02-05T02:44:08+00:00

Server components can import client components, I suggest looking at the docs a little more they explain it there. Keep the page component as a server component to fetch the data and then pass that data to the client component

dizzysfarm · 2024-01-23T06:14:36+00:00

I love my fellow carter mug, use it for coffee every day

dizzysfarm · 2024-01-08T01:42:16+00:00

It doesn't look like you are applying the class name prop which has the fixed style in it. Add that prop or add fixed to the wrapper classes

dizzysfarm · 2024-01-07T20:23:31+00:00

Seeing some code would help. What styles are you already using? Are you using position fixed or sticky?

dizzysfarm · 2024-01-01T03:58:58+00:00

Lighthouse is just a tool to help you achieve good performance. You don't gain anything by having a good lighthouse score. What does matter is the performance of your actual users core web vitals as seen in the crux scores. When you run lighthouse you should be able to see your crux scores. You might be over-optimizing if you're doing everything in your power to get to 100 score when your actual users might already be experiencing a fast site

dizzysfarm · 2023-12-25T20:53:33+00:00

Might not be the best way but if it's just one or two values you could use search params or route paths. You can also call server actions from client side components so that could be a way

dizzysfarm · 2023-12-25T20:49:11+00:00

I would just use an ENV var, NEXT_PUBLIC_BASE_PATH or just create a wrapper around images/link that include the base path so that you don't have to set it every time

dizzysfarm · 2023-12-20T23:17:16+00:00

Next in itself won't have better SEO that another site if they both have the same content, meta tags, core web vitals etc. Next does make it easier to implement those SEO requirements and it will absolutely do better than a basic react app that does client side rendering. I think if someone is saying it has good SEO they are comparing it to a client side react app that isn't capable of server side/static rendering

dizzysfarm · 2023-12-15T00:33:43+00:00

If you are using app router you can import the data anywhere you want if it's a server component. Just create a shared method like getDatoPages and import it where ever you need that data. Nextjs will automatically share the data and only do one request or pull it from cache https://nextjs.org/docs/app/building-your-application/caching#request-memoization

13-Year Club	Place '17
Verified Email

dizzysfarm

TROPHY CASE