Build errors when project contains a symlink

[acifani]

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

> [email protected] 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

[acifani]

Fixed recently 👍

[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>

[kjmph]

This still happens to me with broken links.

For instance:

host:next.js kjmph$ ln -s notexists examples/basic-css/pages/testfile
host:next.js kjmph$ yarn next ./examples/basic-css/
yarn run v1.22.10
$ node --trace-deprecation packages/next/dist/bin/next ./examples/basic-css/
ready - started server on http://localhost:3000
[Error: ENOENT: no such file or directory, stat '/home/kjmph/next.js/examples/basic-css/pages/testfile'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/home/kjmph/next.js/examples/basic-css/pages/testfile'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[quantizor]

@acifani this should be reopened

[MaxiSantos]

in your next.config.js add this

const { i18n } = require('./next-i18next.config');

module.exports = {
  ...
  webpack: (config, { buildId, dev }) => {
    config.resolve.symlinks = false
    return config
  }
}

[kjmph]

Before this gets locked and unable to comment, like #15278, disabling symlinks isn't always appropriate. I believe pnpm uses them extensively, plus, new versions of Next.js use SWC extensively, and webpack isn't even installed with latest (v12.0.9 at this time).

The problem with broken links and emacs lock files is this code:

next.js/packages/next/lib/recursive-readdir.ts

Lines 30 to 31 in b60c943

	const stats = await promises.stat(absolutePath)
	isDirectory = stats.isDirectory()

When a symlink is encountered, recursiveReadDir tries and stat the file. This can lead to ENOENT exceptions. Either all callers of this function should pass in configurable parameters for the ignore RegExp. Which is unlikely, see here:

next.js/packages/next/lib/typescript/getTypeScriptIntent.ts

Lines 29 to 33 in b60c943

	const typescriptFiles = await recursiveReadDir(
	pagesDir,
	/.*\.(ts|tsx)$/,
	/(node_modules|.*\.d\.ts)/
	)

Or!!! recursiveReadDir should gobble those ENOENT exceptions and let us move along in the build. Please don't kill this thread too.

[github-actions]

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.