You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the workspace based approach to identify nx projects, nx does not seem to be properly identifying projects based on items in the workspaces property of package.json.
Given a file system of the below, the following issues arise:
Scenario 1 - Basic project
"workspaces": [
"packages/*",
"packages/ui/*"
]
Actual Behavior - Works as expected, all 4 projects are properly identified
Scenario 2 - Adjusted workspaces to only include root level folders inside of packages directory
"workspaces": [
"packages/*"
]
Actual Behavior: @nx-workspaces-not-honored/uilib1 and @nx-workspaces-not-honored/uilib2 are listed in projects with their fully qualified names
Scenario 3 - Added @nx/eslint to packagelib2
"workspaces": [
"packages/*"
]
Actual Behavior: @nx-workspaces-not-honored/packagelib1fake is listed as a project in addition to @nx-workspaces-not-honored/uilib1 and @nx-workspaces-not-honored/uilib2 all with their fully qualified names.
Actual Behavior: @nx-workspaces-not-honored/packagelib1fake is listed as a project in addition to @nx-workspaces-not-honored/uilib1 and @nx-workspaces-not-honored/uilib2 all with their fully qualified names.
Expected Behavior
Scenario 1 - Works as expected
Scenario 2 - Only packagelib1 and packagelib2 should be listed as projects
Scenario 3 - Only packagelib1 and packagelib2 should be listed as projects
Scenario 4 - Only packagelib1 and packagelib2 should be listed as projects
This seems to be two different issues since it requires eslint to trigger Scenario 3. If it's preferred that I create a separate issue for that one, just let me know, happy to do so.
The text was updated successfully, but these errors were encountered:
Current Behavior
Using the workspace based approach to identify nx projects, nx does not seem to be properly identifying projects based on items in the workspaces property of
package.json
.Given a file system of the below, the following issues arise:
Scenario 1 - Basic project
Actual Behavior - Works as expected, all 4 projects are properly identified
Scenario 2 - Adjusted workspaces to only include root level folders inside of packages directory
Actual Behavior:
@nx-workspaces-not-honored/uilib1
and@nx-workspaces-not-honored/uilib2
are listed in projects with their fully qualified namesScenario 3 - Added
@nx/eslint
topackagelib2
Actual Behavior:
@nx-workspaces-not-honored/packagelib1fake
is listed as a project in addition to@nx-workspaces-not-honored/uilib1
and@nx-workspaces-not-honored/uilib2
all with their fully qualified names.Scenario 4 - Explicitly exclude workspace folders
Actual Behavior:
@nx-workspaces-not-honored/packagelib1fake
is listed as a project in addition to@nx-workspaces-not-honored/uilib1
and@nx-workspaces-not-honored/uilib2
all with their fully qualified names.Expected Behavior
packagelib1
andpackagelib2
should be listed as projectspackagelib1
andpackagelib2
should be listed as projectspackagelib1
andpackagelib2
should be listed as projectsGitHub Repo
https://github.com/techfg/nx-workspaces-not-honored-repro
Steps to Reproduce
Scenario 1
Scenario 2
Scenario 3
Scenario 4
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
eslint
to trigger Scenario 3. If it's preferred that I create a separate issue for that one, just let me know, happy to do so.The text was updated successfully, but these errors were encountered: