not-found.tsx
Unanswered
Spectacled bear posted this in #help-forum
Spectacled bearOP
### Setup:
- next version ^13.4.19
My project folder structure is:
./src/app/[locale]/...
./src/app/not-found.tsx
./src/app/error.tsx
./src/app/global-error.tsx
./src/app/layout.tsx
### Issue
When I've tried to start my app in such config, I received an 500 error in client and an error as at screenshot in server-console.
After removing not-found.tsx – everything works clear.
I've already tried to rename the file to js/ts but it doesn't help.
The main weird trouble as for me is that the mentioned error relates to pages-routing as I'm guessing, but using app-routing in my case.
- next version ^13.4.19
My project folder structure is:
./src/app/[locale]/...
./src/app/not-found.tsx
./src/app/error.tsx
./src/app/global-error.tsx
./src/app/layout.tsx
### Issue
When I've tried to start my app in such config, I received an 500 error in client and an error as at screenshot in server-console.
After removing not-found.tsx – everything works clear.
I've already tried to rename the file to js/ts but it doesn't help.
The main weird trouble as for me is that the mentioned error relates to pages-routing as I'm guessing, but using app-routing in my case.
11 Replies
Spectacled bearOP
here is the error
@joulev Can you give us a repro repository?
Spectacled bearOP
what files do you need?
@Spectacled bear what files do you need?
A minimal reproduction repository, not just files
Because I need to see the project structure
@joulev A minimal reproduction **repository**, not just files
Spectacled bearOP
I'm afraid it might be difficult due to nda(
But I can to provide some files for it.
Important note that this setup starts on Docker with node 16 alpine
But I can to provide some files for it.
Important note that this setup starts on Docker with node 16 alpine
@Spectacled bear I'm afraid it might be difficult due to nda(
But I can to provide some files for it.
Important note that this setup starts on Docker with node 16 alpine
I never told you to give me your work repo. It would be too big for me to have time to look at anyway. What I want is a minimal repo void of any secret stuff/complex set up that still reproduces the problem. See also https://nextjs-discord-common-questions.joulev.dev/how-to-create-a-minimal-reproduction-repository
Without a minimal reproduction I have to tell you I’m unable to help with anything, and I doubt anyone here would have the seemingly magical power to do that, due to the severe lack of information for debugging. You make the decision