The most expedient way would be to put the language change button component into its own file marked 'use client'

use client part is im ok with it problem starts with this they removed aspath query pathname etc from router object in app

Yes, I suppose that does make sense. asPath would not work so great with server components

do you not want to have the language tagged anywhere in the URL?

i actually want it :/

hmmm, it looks like they just want you to use a middleware for internationalization https://nextjs.org/docs/app/building-your-application/routing/internationalization#routing-overview

this looks like a very big project for you 😭

nah middleware part does not make it sense since if a user lets say from france wants it to use it with english they should not stuck with french tho

I actually agree, but you could just link from /fr/page to /en/page in this example

the middleware only switches if there is no language path tag

<Link> for dynamic paths lets you just put the resolved path in the strin g

you dont have to do the stuff with /[locale]/page asPath=/en/page ...

i do that stuff for select sadly select onChange={(e) =>
router.push({ pathname, query }, asPath, {
locale: e.target.value,
})
}

lets say that switch a the locale in middle of a route in pages route it switches where there user they are and thats a nice ux but if im gonna switch lang prob i need to send to root page right?

I would switch to the equivalent page if such a page exists, or dump them to the home page otherwise

and if they don't like that they can hit the back button

the original part how i handle the switch

yeah, that makes sense entirely

so, how do i do it with your way looking to docs they didn't mentioned switching locales with link component

so, basically next.js has gotten rid of the localization feature in the app directory as it is redundant with the release of middleware

you have to put the middleware from the linked page, and then the router.push just takes a plain ol' url for the page with a language tag if you want to switch

do they added rsc to pages too right?

like pages in the /pages dir and not the /app dir?

yeah

no, everything in /pages works exactly the same as Next 12 basically

and also no, the stuff in /app and in /pages are totally separate, almost like two separate React apps

that is what I meant that it will be a lot of work, it doesn't look like there is an incremental upgrade path

I am working on ripping the Redux out of an app to port it

yeah i know just asked to be sure i guess if they ever remove it i will probably switch or stick with the current version that im using

I was getting pretty serious about svelte in the interim before the /app thing was marked stable, but ultimately came back due to a lack of supporting libraries

in my project i already have a seperate backend, later on if they kill it i will just get rid of the next js totally and add react or svelte to directly backend to create achiving ssr i guess

those my options since i tried today the app router whats the benefit of using to test it

for my case None

good luck!