
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
The nx-rescope
tool is designed to assist you in migrating your workspace to the new scope format introduced in Nx version 16. This update involved transitioning the @nrwl
packages to the @nx
scope. To learn more about this change, refer to the official documentation.
npx nx-rescope
Nx already has a built-in command to apply these migrations
nx migrate latest
npx nx migrate --run-migrations --create-commits
The nx-rescope
tool will do the following:
@nrwl
dependencies to @nx
@nrwl
devDependencies to @nx
@nrwl
peerDependencies to @nx
@nrwl
overrides to @nx
(if the --update-overrides
option is enabled)You can check the current supported rescope/rename packages here.
While the nx-rescope
tool assists in migrating your workspace to the new scope format, it does not perform the following actions:
@nrwl
/@nx
packages. It focuses on updating the scope format rather than upgrading the package versions (use nx migrate latest
instead).package.json
files of your individual projects. Only the workspace's package.json
file will be updated during the migration.tsconfig.json
, jest.config.js
, etc. The tool solely focuses on updating the workspace's package.json
file.It's important to note that you may need to handle these aspects manually if necessary.
The recommended approach is to use the nx-rescope
tool in conjunction with the nx migrate latest
command. This will ensure that your workspace is up-to-date with the latest version of Nx and that the scope format is updated accordingly.
To make sure that your workspace is ready for the migration, you can run the following commands in sequence:
nx migrate latest
Then use your package manager of choice to install the new dependencies, and to make sure you are using the latest version of Nx or at least the version 16.0.0:
npm install
# or
yarn install
# or
pnpm install
Finally, run the nx-rescope
tool to update the scope format:
npx nx-rescope
Option | Description |
---|---|
--help | Display a help message |
--dry-run | By using this option, the tool will perform a dry run, meaning it will simulate the changes without modifying the package.json file or installing new dependencies. |
--force | If you encounter any conditions that prevent the execution of the script, you can use the --force option to override these conditions and force the tool to proceed. |
--update-overrides | Enabling this option will update the overrides section of the package.json file, ensuring that it aligns with the new scope format. |
--skip-install | If you don't want the tool to automatically install the new dependencies, you can utilize the --skip-install option. This is useful if you prefer to handle the installation manually. |
Feel free to modify and enhance this readme file according to your specific project requirements.
FAQs
Update your Nx packages to use the new @nx scope (formerly @nrwl).
The npm package nx-rescope receives a total of 0 weekly downloads. As such, nx-rescope popularity was classified as not popular.
We found that nx-rescope demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.