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.

2.1.0 requires vertx, but it is not a dependency in package.json

See original GitHub issue

I get an error like this when using axios, and it seems to come from this library.

"./~/axios/~/es6-promise/dist/es6-promise.js
Module not found: Error: Cannot resolve module 'vertx' in /home/user/workspaces/company/project/node_modules/axios/node_modules/es6-promise/dist
resolve module vertx in /home/user/workspaces/company/project/node_modules/axios/node_modules/es6-promise/dist
  looking for modules in /home/user/workspaces/company/project/node_modules/axios/node_modules
    /home/user/workspaces/company/project/node_modules/axios/node_modules/vertx doesn't exist (module as directory)
    resolve 'file' vertx in /home/user/workspaces/company/project/node_modules/axios/node_modules
      resolve file
        /home/user/workspaces/company/project/node_modules/axios/node_modules/vertx doesn't exist
        /home/user/workspaces/company/project/node_modules/axios/node_modules/vertx.js doesn't exist
        /home/user/workspaces/company/project/node_modules/axios/node_modules/vertx.json doesn't exist
  looking for modules in /home/user/workspaces/company/project/node_modules
    /home/user/workspaces/company/project/node_modules/vertx doesn't exist (module as directory)
    resolve 'file' vertx in /home/user/workspaces/company/project/node_modules
      resolve file
        /home/user/workspaces/company/project/node_modules/vertx doesn't exist
        /home/user/workspaces/company/project/node_modules/vertx.js doesn't exist
        /home/user/workspaces/company/project/node_modules/vertx.json doesn't exist
  looking for modules in /home/user/node_modules
    /home/user/node_modules/vertx doesn't exist (module as directory)
    resolve 'file' vertx in /home/user/node_modules
      resolve file
        /home/user/node_modules/vertx doesn't exist
        /home/user/node_modules/vertx.js doesn't exist
        /home/user/node_modules/vertx.json doesn't exist
[/home/user/workspaces/company/project/node_modules/axios/node_modules/vertx]
[/home/user/workspaces/company/project/node_modules/axios/node_modules/vertx]
[/home/user/workspaces/company/project/node_modules/axios/node_modules/vertx.js]
[/home/user/workspaces/company/project/node_modules/axios/node_modules/vertx.json]
[/home/user/workspaces/company/project/node_modules/vertx]
[/home/user/workspaces/company/project/node_modules/vertx]
[/home/user/workspaces/company/project/node_modules/vertx.js]
[/home/user/workspaces/company/project/node_modules/vertx.json]
[/home/user/node_modules/vertx]
[/home/user/node_modules/vertx]
[/home/user/node_modules/vertx.js]
[/home/user/node_modules/vertx.json]
 @ ./~/axios/~/es6-promise/dist/es6-promise.js 125:20-30"

Issue Analytics

State:
Created 8 years ago
Reactions:2
Comments:16 (4 by maintainers)

Top GitHub Comments

6reactions

0xRcommented, Jul 4, 2017

Instead of dynamically attempting to load vertx to see if it is installed we could just make possible to pass a vertx implementation. This could be part of some configuration function call. This solves issues with bundlers and makes the usage of vertx by this library more explicit. It seems webpack is just a bit smarter than browserify if it understands this code.

6reactions

axe312gercommented, Apr 6, 2017

So what about getting rid of a JVM dependeny definetly only a small portion of people are using?

Or at least requiring it in a way, it won’t throw errors/warnings on a “normal” build process with babel & some bundler? (webpack, rollup, …)

Top Results From Across the Web

Package json dependencies don't match - Stack Overflow

I've deleted both node-modules and the yarn.lock file and it doesnt seem to change things. I'm curious why there is a difference there....

vertx module not found · Issue #100 · stefanpenner/es6-promise

jacob-israel-turner mentioned this issue on Apr 17, 2015. 2.1.0 requires vertx, but it is not a dependency in package.json #106.

package.json - npm Docs

This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just a...

Vert.x 3 says “hello” to NPM users | Blog

In this article, I'll be demonstrating how NPM users can quickly get started with vert.x . You will see that it is not...

Package List — Spack 0.20.0.dev0 documentation

libFLAME is a C-only implementation and does not depend on any external ... Versions: 2.1.0, 2.0.1, 2.0.0; Build Dependencies: cuda, cmake, ninja, mpi,...