fix(module-federation): collect secondary entry points from exports #26878

[Coly010]

Current Behavior

Some packages that use exports in the package.json may point to a directory such as esm/<entrypoint>.
They would still be imported such as mypackage/secondary-point.
This needs to be shared still for Module Federation.

However, our current logic for finding secondary entry points for packages looks at the sub dirs of the package and tries to match it with the exports fiels.

Therefore if mypackage/secondary-point was set up such that

"./secondary-point": {
  default: "esm/secondary-point/index.mjs"
}

then it would never be found correctly, causing share problems.

Expected Behavior

exports of secondary entrypoints should be shared correctly

Related Issue(s)

Fixes #26878

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Sep 19, 2024 5:26pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit ab2052e. 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 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=7d0d834e425488c77a7f9f6360ca51f2f87cdda7 --head=ab2052e7bd92505487f7db692d43bb611ede7aef --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=7d0d834e425488c77a7f9f6360ca51f2f87cdda7 --head=ab2052e7bd92505487f7db692d43bb611ede7aef
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.