npm / cli

the package manager for JavaScript
https://docs.npmjs.com/cli/
Other
8.38k stars 3.11k forks source link

npm ERR! cb() never called! #3027

Closed shakeelahmed91191 closed 3 years ago

shakeelahmed91191 commented 3 years ago

Current Behavior:

Expected Behavior:

Steps To Reproduce:

Environment:

shakeelahmed91191 commented 3 years ago

:\freelancing\gatsby-pro-site>npm install -verbose npm verb cli [ npm verb cli 'C:\Program Files\nodejs\node.exe', npm verb cli 'C:\Users\GB\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js', npm verb cli 'install', npm verb cli '-verbose' npm verb cli ] npm info using npm@7.8.0 npm info using node@v14.16.0 npm timing npm:load:whichnode Completed in 2ms npm timing config:load:defaults Completed in 4ms npm timing config:load:file:C:\Users\GB\AppData\Roaming\npm\node_modules\npm\npmrc Completed in 3ms npm timing config:load:builtin Completed in 3ms npm timing config:load:cli Completed in 4ms npm timing config:load:env Completed in 1ms npm timing config:load:file:F:\freelancing\gatsby-pro-site.npmrc Completed in 1ms npm timing config:load:project Completed in 2ms npm timing config:load:file:C:\Users\GB.npmrc Completed in 0ms npm timing config:load:user Completed in 0ms npm timing config:load:file:C:\Users\GB\AppData\Roaming\npm\etc\npmrc Completed in 2ms npm timing config:load:global Completed in 2ms npm timing config:load:validate Completed in 3ms npm timing config:load:setEnvs Completed in 2ms npm timing config:load Completed in 21ms npm timing npm:load:configload Completed in 21ms npm timing npm:load:setTitle Completed in 1ms npm timing npm:load:setupLog Completed in 3ms npm timing npm:load:cleanupLog Completed in 4ms npm timing npm:load:configScope Completed in 0ms npm timing npm:load:projectScope Completed in 1ms npm timing npm:load Completed in 64ms npm timing config:load:flatten Completed in 4ms npm timing arborist:ctor Completed in 1ms npm timing arborist:ctor Completed in 0ms npm timing idealTree:init Completed in 8243ms npm timing idealTree:userRequests Completed in 1ms npm http fetch GET 200 http://registry.npmjs.org/prettier 180069ms

shakeelahmed91191 commented 3 years ago

npm install in not working hange here idealTree:gatsby-starter-netlify-cms: sill idealTree buildDeps

ljharb commented 3 years ago

417.

shakeelahmed91191 commented 3 years ago

Actually I am getting started in gatsby , at first I install packages via yarn , its working perfectly , as per Clint requirement he wants me to install packages through npm install so error mention above occurs again and again.

shakeelahmed91191 commented 3 years ago

417.

please help me why I dont know via yarn Is working perfectly but with npm its is not working

ljharb commented 3 years ago

Can you fill out the issue template in its entirety?

shakeelahmed91191 commented 3 years ago

npm install npm ERR! code E405 npm ERR! 405 Method Not Allowed - GET http://registry.npmjs.org/prettier/gatsby

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\GB\AppData\Local\npm-cache_logs\2021-04-04T20_19_08_050Z-debug.log

ljharb commented 3 years ago

prettier/gatsby isn't a thing. What's in your package.json?

shakeelahmed91191 commented 3 years ago

{ "name": "gatsby-starter-default", "private": true, "description": "A simple starter to get up and developing quickly with Gatsby", "version": "0.1.0", "author": "Kyle Mathews mathews.kyle@gmail.com", "dependencies": { "@material-ui/core": "^4.7.0", "@material-ui/icons": "^4.5.1", "axios": "^0.19.0", "bootstrap": "^4.4.1", "gatsby": "^2.18.4", "gatsby-image": "^2.2.34",

"gatsby-plugin-google-tagmanager": "^2.10.0",
"gatsby-plugin-layout": "^1.1.21",
"gatsby-plugin-manifest": "^2.2.30",
"gatsby-plugin-offline": "^3.0.24",
"gatsby-plugin-page-transitions": "^1.0.8",
"gatsby-plugin-react-helmet": "^3.1.16",
"gatsby-plugin-sass": "^2.1.24",
"gatsby-plugin-sharp": "^2.3.4",
"gatsby-plugin-smoothscroll": "^1.0.3",
"gatsby-source-filesystem": "^2.1.39",
"gatsby-transformer-sharp": "^2.3.6",
"i18next": "^19.0.3",
"i18next-browser-languagedetector": "^4.0.1",
"i18next-locize-backend": "^3.0.0",
"i18next-xhr-backend": "^3.2.2",
"locize-editor": "^3.0.0",
"lodash": "^4.17.15",
"material-ui-icons": "^1.0.0-beta.36",
"node-sass": "^4.13.0",
"prop-types": "^15.7.2",
"react": "^16.12.0",
"react-calendar": "^2.19.2",
"react-date-picker": "^7.9.0",
"react-dom": "^16.12.0",
"react-dropdown-select": "^3.8.1",
"react-dropzone": "^10.2.1",
"react-dropzone-uploader": "^2.11.0",
"react-helmet": "^5.2.1",
"react-i18next": "^8.3.8",
"react-native-calendars": "^1.214.0",
"react-phone-input-2": "^2.11.0",
"react-places-autocomplete": "^7.2.1",
"react-redux": "^7.1.3",
"react-spinkit": "^3.0.0",
"redux-thunk": "^2.3.0",
"scroll-to-element": "^2.0.3",
"smooth-scroll": "^16.1.0",
"superagent": "^5.1.2"

}, "devDependencies": { "prettier": "^1.19.1" }, "keywords": [ "gatsby" ], "license": "MIT", "scripts": { "build": "gatsby build", "develop": "gatsby develop", "format": "prettier --write \"*/.{js,jsx,json,md}\"", "vicente": "GATSBY_API_URL=http://d51vicente.schrott:3000 gatsby develop -H d51vicente.schrott -p 8000", "javi": "GATSBY_API_URL=http://localhost:3000 gatsby develop -H jarstorm -p 8000", "start": "GATSBY_API_URL=http://localhost:3000 npm run develop", "serve": "gatsby serve", "clean": "gatsby clean", "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1" }, "repository": { "type": "git", "url": "https://github.com/gatsbyjs/gatsby-starter-default" }, "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" } }

ljharb commented 3 years ago

and what version of node/npm are you using? (node -v, npm -v)

shakeelahmed91191 commented 3 years ago

npm -v 7.8.0

node -v v14.16.0

shakeelahmed91191 commented 3 years ago

Even I install grab new start up tamplete but still its give me this error

F:\gatsby\gatsby-starter-netlify-cms>npm install [..................] - idealTree:gatsby-starter-netlify-cms: sill idealTree buildDeps

nlf commented 3 years ago

i'm unable to reproduce this.

are you using a proxy? can you share the output of npm config ls?

razakadam74 commented 3 years ago

I don't know if this helps in any way however I think it might help with your investigations. I was facing same issue using vscode terminal to run npm install. It worked when I run it in a Powershell outside vscode.

VScode Env: image