Build errors when project contains a symlink

Bug report

Describe the bug

Next commands build and dev error out whenever there is a symbolic link in a directory within the project

To Reproduce

Either

• use my example repo https://github.com/acifani/next-symlink-bug
• create a symbolic link (ln -s source_file dest_file) in an directory of an existing project

Expected behavior

Build should not error out, whether or not it should follow the symlink I don’t know

Screenshots

Error output:

❯ npm run build

> next-symlink@1.0.0 build /path/to/repo/next-symlink-bug
> next build

> Build error occurred
{ [Error: ENOENT: no such file or directory, stat '/path/to/repo/next-symlink-bug/some_dir/some_symlink']
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path:
   '/path/to/repo/next-symlink-bug/some_dir/some_symlink' }

System information

• OS: macOS 10.14.5
• Version of Next.js: ^9

Additional context

The exception is caused by the build checking for possible TypeScript files. More specifically, by fs.statSync in this line. There’s a separate command, fs.symlinkLink, available for symlinks

[reflash]

Same appears to happen when I have a symlink to a folder:

Error! ENOENT: no such file or directory, stat '/home/runner/work/<projname>/<projname>/<symlink>

[github-actions[bot]]

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