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

cannot install.. persistently fails #175

Open
nhhockeyplayer opened this issue Jul 15, 2024 · 2 comments
Open

cannot install.. persistently fails #175

nhhockeyplayer opened this issue Jul 15, 2024 · 2 comments
Labels

Comments

@nhhockeyplayer
Copy link

nhhockeyplayer commented Jul 15, 2024

a follow up to this one....

#174

im bamboozled and chose to nuke everything and do a fresh from the start installation of node.js version latest 22 after a sound machine cleanup caches and everything

meanstack02@admin meanstacknh % npm config get prefix
/usr/local
meanstack02@admin meanstacknh % npm -g root
/usr/local/lib/node_modules
meanstack02@admin meanstacknh % which nx
/usr/local/bin/nx
meanstack02@admin meanstacknh % which npm
/usr/local/bin/npm
meanstack02@admin meanstacknh % which yarn
/usr/local/bin/yarn
meanstack02@admin meanstacknh % which json-graphql-server
json-graphql-server not found
meanstack02@admin meanstacknh % npm install -g json-graphql-server
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: [email protected]
npm warn Found: [email protected]
npm warn node_modules/json-graphql-server/node_modules/graphql
npm warn   graphql@"^16.8.1" from [email protected]
npm warn   node_modules/json-graphql-server
npm warn     json-graphql-server@"*" from the root project
npm warn   7 more (@apollo/client, @graphql-tools/schema, graphql-tag, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^14.4.1" from [email protected]
npm warn node_modules/json-graphql-server/node_modules/express-graphql
npm warn   express-graphql@"^0.9.0" from [email protected]
npm warn   node_modules/json-graphql-server
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/graphql
npm warn   peer graphql@"^14.4.1" from [email protected]
npm warn   node_modules/json-graphql-server/node_modules/express-graphql
npm warn     express-graphql@"^0.9.0" from [email protected]
npm warn     node_modules/json-graphql-server
npm warn deprecated [email protected]: This is probably built in to whatever tool you're using. If you still need it... idk
npm warn deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated [email protected]: This package is no longer maintained. We recommend using `graphql-http` instead. Please consult the migration document https://github.com/graphql/graphql-http#migrating-express-grpahql.

changed 116 packages in 4s

13 packages are looking for funding
  run `npm fund` for details
meanstack02@admin meanstacknh % which json-graphql-server         
json-graphql-server not found
meanstack02@admin meanstacknh % 

any help is greatly appreciated

any other package installation works fine
all instances of pnpm and earlier versions of yarn nuked... below is nx report

here is my $PATH
/Users/meanstack02/.yarn/bin:/Users/meanstack02/.config/yarn/global/node_modules/.bin:/Users/meanstack02/devtools/mongodb-macos-x86_64-5.0.9/bin:/Users/meanstack02/devtools/mongodb-atlas-cli_1.1.2_macos_arm64/bin:/Users/meanstack02/devtools/mongosh-1.5.0-darwin-x64/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Applications/Postgres.app/Contents/Versions/latest/bin

% nx report

 NX   Report complete - copy this into the issue template

Node   : 22.4.1
OS     : darwin-x64
yarn   : 1.22.22

nx (global)        : 19.4.3
nx                 : 19.4.3
@nx/js             : 19.4.3
@nx/jest           : 19.4.3
@nx/linter         : 19.4.3
@nx/eslint         : 19.4.3
@nx/workspace      : 19.4.3
@nx/angular        : 19.4.3
@nx/cypress        : 19.4.3
@nx/devkit         : 19.4.3
@nrwl/devkit       : 13.10.6
@nx/eslint-plugin  : 19.4.3
@nx/express        : 19.4.3
@nx/nest           : 19.4.3
@nx/node           : 19.4.3
@nx/storybook      : 19.4.3
@nrwl/tao          : 19.4.3
@nx/web            : 19.4.3
@nx/webpack        : 19.4.3
typescript         : 5.4.5
---------------------------------------
Registered Plugins:
@nx/cypress/plugin
@nx/eslint/plugin
---------------------------------------
Community plugins:
@compodoc/compodoc                    : 1.1.25
@fortawesome/angular-fontawesome      : 0.11.1
@ionic/angular                        : 6.7.5
@jsverse/transloco                    : 7.4.2
@ngrx/component                       : 18.0.1
@ngrx/component-store                 : 18.0.1
@ngrx/effects                         : 18.0.1
@ngrx/entity                          : 18.0.1
@ngrx/operators                       : 18.0.1
@ngrx/router-store                    : 18.0.1
@ngrx/schematics                      : 18.0.1
@ngrx/store                           : 18.0.1
@ngrx/store-devtools                  : 18.0.1
@nxtend/capacitor                     : 13.0.0
@nxtend/ionic-angular                 : 13.1.0
@storybook/angular                    : 7.6.6
angular-builder-custom-terser-options : 1.0.1
apollo-angular                        : 7.0.2
---------------------------------------
The following packages should match the installed version of nx
  - @nrwl/[email protected]

To fix this, run `nx migrate [email protected]`
@nhhockeyplayer
Copy link
Author

in order to penetrate and get this running I have to fabricate and execute the following:

Node.js v22.4.1

meanstack02@admin meanstacknh % node /usr/local/lib/node_modules/json-graphql-server/bin/json-graphql-server.cjs .bff/data.js --p 3333 --h localhost
GraphQL server running with your data at http://localhost:3000/

I know its something simple but these package managers should be wipeout tolerant and its not I could sit and count the points of failure in the design intrinsically, extrinsically locally remotely inside out up and down and its exhausting

not this products fault... bad package mgr design fault

@fzaninotto
Copy link
Member

Confirmed, thanks for the report.

@fzaninotto fzaninotto added the Bug label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants