Current Behavior

nx init always either installs next or latest versions of Nx. The intent here is that running npx nx init should always provide the latest version of Nx, and we added a condition to use next if we detected a beta version of Nx was running to facilitate easier testing of RC and beta releases. The full logic to determine which version of Nx to setup is below:

const version =
    process.env.NX_VERSION ?? (prerelease(nxVersion) ? 'next' : 'latest');

The goal here was to avoid hitting the npx cache and accidentally creating new workspaces with an older Nx version. This logic falls apart a bit when considering prereleases though, as npx nx@next init would always check the tag to make sure its up to date rather than using a cached version. This is the case when providing any tag to npx.

A bad side effect of the above is that when trying to test PR builds and the like, nx init will never setup the PR build when running npx nx@0.0.0-pr.... opting instead to setup next.

Expected Behavior

Running npx nx@0.0.0-pr.... init sets up an nx workspace using the specified PR release.

Related Issue(s)

Fixes #