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.

Missing dependency for Axios 0.16.3

See original GitHub issue

Our app has its contentful-management version set to 3.9.2 in an npm-shrinkwrap file. We realized today that this version depends on a version of Axios that seems to have been forked by Contentful but also that doesn’t currently exist (0.16.3).

I went and looked at your fork and I can’t see anything about 0.16.3 but I did find one other project on github with 0.16.3 referenced in their yarn.lock file and it’s referencing your fork.

Any insight would be helpful. I’m nervous to npm install and regenerate my shrinkwrap since we have a lot of dependencies.

Edit: I got this working by creating a temporary project and generating a shrinkwrap.json file from a package.json with contentful-management 3.9.2. I then hacked the axios dependency from it into my existing shrinkwrap file.

My old dependency for Axios looked like this in the npm-shrinkwrap.json:

"axios": {
          "version": "0.16.3",
          "from": "contentful/axios#fix/https-via-http-proxy",
          "resolved": "git://"

It now looks like this:

"axios": {
          "version": "0.16.2",
          "from": "contentful/axios#fix/https-via-http-proxy",
          "resolved": "git://"

It makes me really nervous that I’m referencing specific commits that can disappear.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

dustinaleksiukcommented, Nov 20, 2017

Hi @Khaledgarbaya,

Thank you for that reply. I actually tried upgrading last week and I saw that my shrinkwrap file still references a git commit directly. I’ll commit the upgrade though and hope that the axios git commits don’t disappear.

Khaledgarbayacommented, Nov 17, 2017

Hi @dustinaleksiuk, That should be fixed permanently now in v4.1.2. Sorry about any inconveniences.

Best, Khaled

Read more comments on GitHub >

github_iconTop Results From Across the Web

axios - gulp builds incomplete when building new components
This issue has been resolved by adding the following to the build task: return browserify(entry, {debug:true}) .require('.
Read more >
axios-mock-server - npm Package Health Analysis - Snyk
0.16.3 ... All security vulnerabilities belong to production dependencies of direct and ... Looks like axios-mock-server is missing a security policy.
Read more >
0.16.2 - axios - npm
Promise based HTTP client for the browser and node.js. Latest version: 1.2.1, last published: 8 days ago. Start using axios in your project ......
Read more >
axios-mock-server v0.19.1 Bundlephobia
Size of axios-mock-server v0.19.1 is 14.4 kB (minified), and 4.0 kB when compressed using ... Ignoring the size of missing dependency axios ....
Read more >
failed to initialize react-native-reanimated library -
Plugins section in Android main project build.gradle and missing modules ... Installing dependencies... yarn install v1.13.0 info No lockfile found.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found