Had this exact problem a few months ago - drove me nuts for hours! You’re using the full GitHub URL, but npm doesn’t like that. Use the shorthand instead: npm install expressjs/express. Just tell npm the organization/repo name and it’ll handle the rest. The format’s always npm install username/repository-name. Also check if there’s actually a package.json in the root - some GitHub repos aren’t meant to be npm packages. The shorthand usually fixes those ENOENT errors since npm fetches the repo differently.
The ENOENT error indicates that npm cannot locate the package.json file during extraction, which might suggest an issue with how the GitHub repository is structured or with the download process itself. Consider using a specified branch in your command, such as npm install https://github.com/visionmedia/express#master, or try the git protocol by using npm install git+https://github.com/visionmedia/express.git. Additionally, clearing the npm cache with npm cache clean --force could help resolve the issue. These steps can assist npm in properly extracting the files needed.