#moving to v13 questions

18 messages · Page 1 of 1 (latest)

wanton badger
#

Hey, i want to move to v13 from v12 and im currently using the old pages structure but i prefer the app/ one, though i got some questions about the new app/ structure;
1, most of my app components are client based, 90% are using hooks and etc that the server/default components.
is that ok to mark 90% of the components as client with the 'client' tag above? isn't that will ruin the v13 structure or slow the application?
2, if im not currently using the new app/ folder for my pages/components, all of my components and pages are automatically defined as client and not server components?
3, is it possible to disable the 'use client' mark or change that? i know its sounds weird but since most of my files are client based, i prefer mark the server based components with 'use server' or something like that instead, so i will not have to mark with 'use client' every new component i make..

Thanks!

warm finch
#

The new /app structure seems to be a beta feature, based on what I can see, so I wouldn't use it in production just yet

wanton badger
# warm finch The new /app structure seems to be a beta feature, based on what I can see, so I...

sadly I really don't like the current approach of making a components folder in the base folder and mix that with the pages components..
I really like the option to make a components folder in each page separately inside the app/ folder..
also idm going into prod with this application, and its currently in a build phase so I rather take the risk, but the only things that stopped me are the question above.

loud schooner
#

is that ok to mark 90% of the components as client with the 'client' tag above?
this is fine, its basically how all components in v12 are

#

if im not currently using the new app/ folder for my pages/components, all of my components and pages are automatically defined as client and not server components?
yeah technically I think so

#

is it possible to disable the 'use client' mark or change that?
I don' t think its possible yet

wanton badger
#

Thanks!

wanton badger
loud schooner
#

the risk is not from running it in production, its mostly for development

wanton badger
#

wdym?

loud schooner
#

I have seen a lot of people complaining about stuff that doesn't work or isn't in a good state yet (like CSS not applying)

#

there are some techs that aren't 100% compatible with server components as well (mostly component libraries)

iron brook
hybrid path
#

it's sounds like a good idea, then progressively you can remove these where you don't need it (progressing to a more granular approach)

noble scarab
halcyon depot
#

Do not use the app directory feature in production yet. It is not ready at all. Among other things, navigation and routing is not great if not broken at the moment even once built for production. But if it is a new project that won't be release for a while go for it. It is great (when it works).

foggy scarab
loud schooner