-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
phantom dependencies in nx and @nrwl packages #12021
Comments
Another one to add (which only came up because I recently did an
And then once my nx was migrated, another one popped up:
|
In addition, another project I'm working on (also on the latest nx) identified the following phantom dependencies:
|
It will be more productive to address these one at a time. Could you please open separate issues for each and describe the situation where it is an issue please? |
Found another: |
@FrozenPandaz I did a migrate recently and I can see that some of these are fixed, but not all of them are. This should not be closed until fixed. |
@FrozenPandaz Also, I do not feel I should have to "describe the situation where it is an issue". If you go to the indicated source file relating to the identified .js file, you should see it doing an import or require for the packages. If these are not listed in the package.json, they should be. |
@FrozenPandaz for example, review this file: https://github.com/nrwl/nx/blob/master/packages/angular/src/executors/ng-packagr-lite/ng-packagr-adjustments/styles/stylesheet-processor.ts#L252. Note that in https://github.com/nrwl/nx/blob/master/packages/angular/package.json, "sass" is not listed as a dependency. This is a phantom dependency and should, at the very least, be listed in peer dependencies. |
@FrozenPandaz This should not be closed. |
@FrozenPandaz it should also not be marked with "more info needed". All the info required is in the original post. When I point out that a file directly depends on a library that is not listed in the |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
When installing
@nrwl/storybook
or@nrwl/workspace
usingpnpm
, there appear to be a couple phantom dependencies.Expected Behavior
If either of these packages publish JS which directly depends on phantom dependencies, those phantom dependencies should be added to the appropriate
package.json
's dependencies (orpeerDependencies
, if appropriate) so that Nrwl Nx can better supportpnpm
as it claims to do. The phantom packages I currently identified are shown below:@nrwl/storybook/src/generators/configuration/configuration.js
directly depends on the followingtslib
@nrwl/workspace/src/utils/ast-utils.js
directly depends on the following@angular-devkit/schematics
@angular-devkit/core
nx/src/adapter/ngcli-adapter.js
directly depends on the following@angular-devkit/core
@angular-devkit/schematics
@angular-devkit/architect
Steps to Reproduce
Here is the original issue that caused me to stumble upon these phantom dependencies. This original issue contains reproduction steps as well as additional information for how to workaround the issue using a
pnpmfile.cjs
file. In that file, I ultimately identified the above offenders.Failure Logs
Environment
The text was updated successfully, but these errors were encountered: