Routes named "children" are not accessible in dev mode

[stage-two]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant Packages:
      next: 13.4.12-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/spring-rgb-6f7kql

To Reproduce

1. Create a file named "children.tsx" under the /pages dir
2. Run next.js dev server
3. Try to navigate to /children page in the browser

Describe the Bug

Routes having /children substring are not accessible in the dev mode.
In the provided codesandbox example routes /children and /profile/children do not work while deliberately misspelled /chiltren works just fine.

Looks like this behaviour was introduced by #52362

Expected Behavior

Pages are accessible in dev/prod mode disregarding their name.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1514

[darshanjain-entrepreneur]

Is this a problem or it is specifically done by next js team

[schlegz]

Can confirm this in my project as well.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.