@disc0dancer.bsky.social
Нема логика ова. Ова се договориле да бојкотираат големопродажници што качуваат цени, не они да качат цени. "Договарањето" ми личи со цел да намалат цени :)
February 27, 2025 at 7:36 PM
Нема логика ова. Ова се договориле да бојкотираат големопродажници што качуваат цени, не они да качат цени. "Договарањето" ми личи со цел да намалат цени :)
Има негде инфо што точно има во забранетиот договор?
February 27, 2025 at 10:34 AM
Има негде инфо што точно има во забранетиот договор?
Weirdly, it doesn't ... at least in my local dev env - haven't deployed this anywhere yet.
Btw, thanks for all the replies - really helpful :)
Btw, thanks for all the replies - really helpful :)
January 28, 2025 at 9:47 PM
Weirdly, it doesn't ... at least in my local dev env - haven't deployed this anywhere yet.
Btw, thanks for all the replies - really helpful :)
Btw, thanks for all the replies - really helpful :)
I can also slap a 'document.title = "blabla"' inside a useEffect hook in each component, and at this point I decided that Vercel sacrificed too much at the alter of server-side rendering which gives you no real benefits and I had to vent a bit....
January 26, 2025 at 9:12 PM
I can also slap a 'document.title = "blabla"' inside a useEffect hook in each component, and at this point I decided that Vercel sacrificed too much at the alter of server-side rendering which gives you no real benefits and I had to vent a bit....
Then, the apollo experimental library itself says: "❗️ We do handle "RSC" and "SSR" use cases as completely separate." - the way I understand that box is that my server components and my 'use client' components should not use the same queries, which for me translates to "rewrite the entire frontend"
January 26, 2025 at 9:12 PM
Then, the apollo experimental library itself says: "❗️ We do handle "RSC" and "SSR" use cases as completely separate." - the way I understand that box is that my server components and my 'use client' components should not use the same queries, which for me translates to "rewrite the entire frontend"
Firstly, there's no way to set meta and page title from the client. This used to work with the <Head> component, and there are some people around the internet which incorrectly suggest to add a <title> component anywhere in the page (it doesn't work). Also - why change something that worked ?!
January 26, 2025 at 9:12 PM
Firstly, there's no way to set meta and page title from the client. This used to work with the <Head> component, and there are some people around the internet which incorrectly suggest to add a <title> component anywhere in the page (it doesn't work). Also - why change something that worked ?!
Needless to say, I'm not a fan of rewriting the whole thing as I have more important things to do. Also, since there are no real benefits from server-side components to the user after they hit the first page, I decided to opt-out of server components. But NextJS makes this difficult ...
January 26, 2025 at 9:12 PM
Needless to say, I'm not a fan of rewriting the whole thing as I have more important things to do. Also, since there are no real benefits from server-side components to the user after they hit the first page, I decided to opt-out of server components. But NextJS makes this difficult ...
With the NextJS server components you now can't use client side anymore. Before, stuff like useEffect was ignored on the sever, but now none of the hooks work, so I have 2 choices: 1) add the 'use client' pragma to all my components or 2) rewrite the entire frontend.
January 26, 2025 at 9:12 PM
With the NextJS server components you now can't use client side anymore. Before, stuff like useEffect was ignored on the sever, but now none of the hooks work, so I have 2 choices: 1) add the 'use client' pragma to all my components or 2) rewrite the entire frontend.
Thank you :) You can correct me if I'm wrong in my thinking. As I said, I have an old NextJS app that I'm trying to move to the App router. The app has a lot of components that fetch data using Apollo at various depths. This works fine with SSR, as I can seed Apollo's cache.
January 26, 2025 at 9:12 PM
Thank you :) You can correct me if I'm wrong in my thinking. As I said, I have an old NextJS app that I'm trying to move to the App router. The app has a lot of components that fetch data using Apollo at various depths. This works fine with SSR, as I can seed Apollo's cache.
I'm using experimental-nextjs-app-support ... but It doesn't solve the problem. Stuff fetched on the server does not exist in the client-side cache. Sure, I can make only server components fetch the data, but that's rewriting most of the app.
January 25, 2025 at 4:58 PM
I'm using experimental-nextjs-app-support ... but It doesn't solve the problem. Stuff fetched on the server does not exist in the client-side cache. Sure, I can make only server components fetch the data, but that's rewriting most of the app.
That requires that none of my top level components are 'use client' which means i need to restructure my whole app, and all i wanted to do is set the page title, which in nextjs is impossible to do client-side. I mean - everything is doable, it's just so much more complicated ...
January 24, 2025 at 10:06 PM
That requires that none of my top level components are 'use client' which means i need to restructure my whole app, and all i wanted to do is set the page title, which in nextjs is impossible to do client-side. I mean - everything is doable, it's just so much more complicated ...
My frontend calls the gql api directly with cors, unfortunately...
January 24, 2025 at 3:38 PM
My frontend calls the gql api directly with cors, unfortunately...
In 2014. Too early :)
January 2, 2025 at 3:15 PM
In 2014. Too early :)
