Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to resolve webpack@fulls1z3/webpack#v2.2.1-harmony

See original GitHub issue

It seems that repository: https://github.com/fulls1z3/webpack was deleted and now trying to install azure-functions-pack from npm always fails.

yarn add azure-functions-pack
[1/4] 🔍  Resolving packages...
error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads ssh://git@github.com/fulls1z3/webpack.git
Directory: /Users/Nelak/github/connector-functions
Output:
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Is there any other way to get azure-functions-pack up and running meanwhile?

Issue Analytics

State:
Created 6 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

davidebbocommented, Sep 15, 2017

@christopheranderson just updated the latest tag to an earlier version without the issue, so it should be fixed now.

0reactions

nelakcommented, Sep 15, 2017

@fulls1z3 thanks for your input @davidebbo solution has worked for me already. The issue was reminiscent of the left-pad issue, lesson learned, I’ll try to make sure to avoid using git dependencies in public packages from now on.

Top Results From Across the Web

Resolve | webpack

When enabled, symlinked resources are resolved to their real path, not their symlinked location. Note that this may cause module resolution to fail...

eslint imports in webpack: Unable to resolve path to module

In the example below, webpack (v2.2.0-rc.3) builds fine, but the test fails because it's "Unable to resolve path to module 'components/Counter'".

Unable to resolve path to module 'webpack-hot-middleware'

I'm working with a fresh Sage install. I've added a few ReactJs related npm packages. When running yarn start the new browser window...

can't resolve 'fs' in webpack | The AI Search Engine You Control

But i can't run webpack dev-server at all and i get lots of Module not found: Error: Can't resolve 'fs' in ./node_modules/bunch-of-folders errors....

resolve-url-loader - npm

But any practical SASS composition will have nested SCSS files, as in the 3rd case. Here Webpack cannot find the asset. Module not...