next.js: global not found in app still includes pages
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro Education
Binaries:
Node: 16.17.1
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 13.4.2
eslint-config-next: 13.3.0
react: 18.2.0
react-dom: 18.2.0
typescript: 5.0.4
Which area(s) of Next.js are affected? (leave empty if unsure)
App directory (appDir: true)
Link to the code that reproduces this issue
https://codesandbox.io/p/sandbox/zealous-scott-vppl6r
To Reproduce
Create a global not found file inside app dir and build the project
Describe the Bug
If you build an entire app only project, it still includes not found route using pages. (Even if I build a page 404, still includes pages dir).
Expected Behavior
To only create files using the app dir (pages is also bringing a lot of js).
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (11 by maintainers)
It’ll be removed eventually, please be patient, there’s much more important issues than an extra file being exported.
@JesseKoldewijn is not about running it, its about the built project
@timneutkens Sorry for the @ mention. But do you know if there are any plans to fix this by chance? 😃