feat(misc): remove @nrwl/ scoped packages (#27858 )

This PR removes the `@nrwl/*` packages. Also cleans up references to the
legacy packages.

NOTE: The rescope page is now under `/deprecated/rescope`. There is
still >1000K monthly traffic to it, which might be due to older Nx
users.

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #

2024-09-27 17:19:01 -04:00

1.6 KiB

Raw Blame History

Update Your Global Nx Installation

There are some cases where an issue could arise when using an outdated global installation of Nx. If the structure of your Nx workspace no longer matches up with what the globally installed copy of Nx expects, it may fail to hand off to your local installation properly and instead error. This commonly results in errors such as:

Could not find Nx modules in this workspace.
The current directory isn't part of an Nx workspace.

If you find yourself in this position, you will need to update your global installation of Nx.

In most cases, you can update a globally installed npm package by rerunning the command you used to install it.

If you cannot remember which package manager you installed Nx globally with or are still encountering issues, you can locate other installations of Nx with these commands:

{% tabs %} {% tab label="npm" %}

npm list --global nx

{% /tab %} {% tab label="yarn" %}

yarn 2+

yarn dlx list nx

yarn 1.x

yarn global list nx

{% /tab %} {% tab label="pnpm" %}

pnpm list --global nx

{% /tab %} {% /tabs %}

You can then remove the extra global installations by running the following commands for the duplicate installations: