Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(core): replace @nrwl with @nx in nx core packages #16344

Merged
merged 1 commit into from
Apr 17, 2023

Conversation

FrozenPandaz
Copy link
Collaborator

Current Behavior

There are still some usages of @nrwl/ in nx, @nx/devkit, create-nx-workspace, and create-nx-plugin.

Expected Behavior

The usages of @nrwl/ have been modified to support @nxinnx, @nx/devkit, create-nx-workspace, and create-nx-plugin`.

Related Issue(s)

Fixes #

@vercel
Copy link

vercel bot commented Apr 17, 2023

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

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Apr 17, 2023 8:47pm

packages/create-nx-plugin/.eslintrc.json Show resolved Hide resolved
packages/nx/presets/npm.json Show resolved Hide resolved
@@ -369,8 +369,8 @@ class TaskHasher {
// if it's "run commands" we skip traversing since we have no info what this command depends on
// for everything else we take the hash of the @nrwl package dependency tree
if (
target.executor.startsWith(`@nrwl/`) &&
target.executor !== `@nrwl/workspace:run-commands`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This always seemed wierd, do we no longer need it? I'd love a breakdown of what it was doing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure we can discuss this offline.

Comment on lines +110 to 112
(pluginName.startsWith('@nx/') || pluginName.startsWith('@nrwl/')
? chalk.dim(` (v${nxVersion})`)
: ''),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated to the actual change - but does this report a bad version for labs packages like @nrwl/deno?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think it does.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree - it also just flat out doesn't report a version for things like nx-dotnet. Here's a fix: #16353

It does unfortunately conflict with this PR - feel free to hold on merging it until after this one and I can fix it up.

@FrozenPandaz FrozenPandaz force-pushed the replace-nx branch 6 times, most recently from 1ab8933 to 8debd07 Compare April 17, 2023 20:18
@FrozenPandaz FrozenPandaz merged commit 4ee1ba5 into nrwl:master Apr 17, 2023
@FrozenPandaz FrozenPandaz deleted the replace-nx branch April 17, 2023 21:28
peppoasap pushed a commit to peppoasap/nx that referenced this pull request Apr 18, 2023
@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants