fix(linter): improve handling of barrel entry point files

[forivall]

Current Behavior

ENOENT or other file reading errors when tsconfig paths are configured in some ways, such as in #12067

Expected Behavior

ESLint should not crash and should gracefully continue

Related Issue(s)

Fixes #12067

[nx-cloud-staging]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit edb815f. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 12 targets

• nx affected --target=e2e --base=82d43aff18bad0501641926ec518869dba0e16e3 --head=edb815ff1cd67ad02414b77cacf67f8a1316bc84 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox,e2e-make-angular-cli-faster --parallel=1
• nx affected --target=test --base=82d43aff18bad0501641926ec518869dba0e16e3 --head=edb815ff1cd67ad02414b77cacf67f8a1316bc84 --parallel=1
• nx affected --target=build --base=82d43aff18bad0501641926ec518869dba0e16e3 --head=edb815ff1cd67ad02414b77cacf67f8a1316bc84 --parallel=3
• nx-cloud record -- yarn depcheck
• nx affected --target=lint --base=82d43aff18bad0501641926ec518869dba0e16e3 --head=edb815ff1cd67ad02414b77cacf67f8a1316bc84 --parallel=3
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn check-lock-files
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=82d43aff18bad0501641926ec518869dba0e16e3 --head=edb815ff1cd67ad02414b77cacf67f8a1316bc84
• nx-cloud record -- yarn check-imports
• nx-cloud record -- yarn documentation
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Oct 12, 2022 at 8:17AM (UTC)

[forivall]

alternatively, do a readdir on the parent directory, and check extensions there.

[meeroslav]

Debugging now on WebStorm, I don't think this solves the issue. It actually hides it and the result is an invalid message being returned by the linter.

The file exists, but readFileSync does not find it, meaning we need to ensure the path is correct and full.

[meeroslav]

Please check #12953 for the solution to the given problem.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.