fix(core): ensure require.resolve('nx') resolves correctly

[ndcunningham]

Current Behavior

When you create a plugin that calls our internal executor for example require.resolve('nx') resolves to {workspaceRoot}/nx.json

This is because tsconfig-paths uses require.extensions which includes .json

    interface RequireExtensions extends Dict<(m: Module, filename: string) => any> {
        '.js': (m: Module, filename: string) => any;
        '.json': (m: Module, filename: string) => any;
        '.node': (m: Module, filename: string) => any;
    }

Expected Behavior

require.resolve('nx') should resolve to nx binary. For example located in node_modules/nx/bin/nx.js

Related Issue(s)

Filed an issue: dividab/tsconfig-paths#255

fixes: #19782

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Oct 23, 2023 7:07pm

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=cc8d8e8f4cedf8dba9cf82118681b7a851bbe3a3 --head=83a40a458c4958d043969356007d9cda2937534b --parallel=1
• nx affected --targets=lint,test,build --base=cc8d8e8f4cedf8dba9cf82118681b7a851bbe3a3 --head=83a40a458c4958d043969356007d9cda2937534b --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=cc8d8e8f4cedf8dba9cf82118681b7a851bbe3a3 --head=83a40a458c4958d043969356007d9cda2937534b
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=cc8d8e8f4cedf8dba9cf82118681b7a851bbe3a3 --head=83a40a458c4958d043969356007d9cda2937534b

---

Sent with 💌 from NxCloud.

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