Can't resolve 'vertx'
See original GitHub issueiv tried doing the
new webpack.IgnorePlugin(/vertx/)
not working for me
Module not found: Error: Can't resolve 'vertx' in '/*******/node_modules/es6-promise/dist'
@ ./node_modules/es6-promise/dist/es6-promise.js 138:16-26
@ ./client/src/App.jsx
@ ./client/src/routes.jsx
@ ./client/src/index.jsx
@ multi ./client/src/index
webpack: Compiled with warnings.```
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:13 (6 by maintainers)
Top Results From Across the Web
vertx module not found when using webpack - Stack Overflow
To resolve the issue: Install @vertx/core ( npm i @vertx/core ). Edit the file ./node_modules/when/lib/env.js , and change line 32 from
Read more >How to fix "error: cannot find symbol import io.vertx.core.json ...
java - How to fix "error: cannot find symbol import io. vertx. core. json" Vertx - Ask Ubuntu.
Read more >Vert.x Core Manual
Even though a Vertx instance maintains multiple event loops, any particular handler will never be executed concurrently, and in most cases (with the...
Read more >Use es6-promise package to avoid webpack warnings - GitLab
Use the es6-promise package to avoid the webpack warning fluff, Module not found: Error: Can't resolve 'vertx'.
Read more >Are there other ways to synchronize operations other than ...
In my Web controller I need to wait for Vert.x (event bus) to send, and process response and I can't just rely on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@stefanpenner I just found this issue today. Any updates on a fix?
@pablohpsilva webpack appears to not respect browserifies
browser
field in this projects package.json. Yes webpack is not browserify, but it either should support this how provide some alternative (ideally support).https://github.com/stefanpenner/es6-promise/blob/e1bb7b6ed5ce7999c1ea1aa2ea5e338e183a3d18/package.json#L53-L55
@TheLarkInn is it intended for webpack to not support this? I suspect if it did, it would support even more browserify-safe packages. If not, is there another configuration based approach which could be used?
Alternatively, is there some heuristic we can rely on to
require
but withoutwebpack
getting confused?