No because how should Next deduce which page to serve for a route like /home/foo.

i dont understand why this only happens with dynamic routes while static routes dont have this problem

to exapand on what near said, think about it like this:
if I go to home/foo, nextjs doesn't know where to take you. Next has no way of knowing if that's an account or a profile. it would be like having two page.js files for the home route. Instead, you could do home/account/[id]/page.js and home/profile/[id]/page.js

pls mark as solution if this helped!

i understand but like why this only happens with dynamic routes while static routes dont have this problem

Because static routes only map to a single unique path.

If I navigate to /home/foo it will attempt to render /home/foo/page.tsx

The route you navigate to maps strictly to a single path in the file system, there are no ambiguous paths there.

Unlike with your example where two distinct pages would be candidates for the same path

I couldn't have said it better

@Gouty oak gall can you share a bit more about your use case? are you trying to display multiple pages on one route?

okay i understand it now kinda lol

just getting started w nextjs and i made those two folders in a same folder, when i went to home/profile, it displayed the contents of account page and when i restarted the server, it THEN only gave me this error

Error: You cannot use different slug names for the same dynamic path ('account' !== 'profile').

soo i was curious, guess we learn smt new everyday

thank you Lucas and Near

o

so

how to mark solved

ok lemme properly answer this for you

yes please

when you do home/[account]/page.tsx

that captures any route that you put after home

okayyyyyyyyy

that's why you can't have multiple

so on one level, we can have only one [] or [...] right

and that doesnt apply to static routes

not sure what [...] is, but sure

catch all 😭

my bad

catch all routes

ooh right ok I didn't see the syntax bc I'm used to seeing a name

yeah that was a bad usage from my end

should have been [...smt]

right

anyways

to mark as solution

you just do this

okay thank you

fyi, dynamic routes opt the page into dynamic rendering, but a page can be opted into dynamic rendering and not be a dynamic route

howww thatt

ig I'm probably just making this more complicated

but just try to read the docs more in general