github npm registry does not allow custom fields on npm view, breaking migrations

[gioragutt]

Current Behavior

Discussion on slack.

nx migrate relies on npm view to get information about migrations to run from updated packages, specifically by getting the ng-update or nx-migration fields.

However, in the case of packages that reside in the github package registry, its implementation of npm view does not return custom fields.

In that case, getting the package with npm view will not fail since npm view does not throw, so it does not fall back to getting the package with package-manager install.

This results in migrations not being picked up.

Expected Behavior

All packages, including those under the github package registry, should allow migrations.

I've been in contact with the github support team, and it's been communicated that exposing arbitrary package.json fields is not prioritized and will not be implemented any time soon.

Given that, my suggestion is to special-case the npm github package registry to opt out of the npm view behavior.

Steps to Reproduce

Failure Logs

There are no failures, as npm view, in this case, acts as if the package has no migrations.

Environment

This is not an NX issue, so it will happen on all versions with the npm view behavior.

[tremppu]

Any updates? Just started using GitHub Packages for our organization and this bug makes life difficult atm...

[github-actions]

This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[EkatZaytseva]

Hey; any update on this? This is definitely not stale as issue is still there.

[AgentEnder]

This was fixed by #16423

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.