Webpack failure with @loaders.gl/images
See original GitHub issueI get this error when attempting to run deck.gl with webpack:
ERROR in ./node_modules/@deck.gl/core/dist/esm/lib/init.js
Module not found: Error: Can't resolve '@loaders.gl/images' in '/Users/<user>/workspace/source/tracegraph/web/src/main/js/visualizer/node_modules/@deck.gl/core/dist/esm/lib'
@ ./node_modules/@deck.gl/core/dist/esm/lib/init.js 2:0-49 25:31-42
@ ./node_modules/@deck.gl/core/dist/esm/index.js
@ ./node_modules/deck.gl/dist/esm/index.js
@ ./src/viz/map/index.js
@ ./src/graphing.js
@ ./src/index.js
I assume I’m missing a rule in webpack config?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
Webpack. Image loading failed - Stack Overflow
Yow broh, you need to use url-loader File loader is for html files and stuff // "url" loader works like "file" loader except...
Read more >Get Started - loaders.gl
You can use your bundler of choice such as webpack or rollup. See the get-started examples for minimal working examples of how to...
Read more >loaders.gl - Yarn
loaders.gl is a framework in the vis.gl framework suite that provides a collection of framework-independent loaders focused on geospatial, 3D and big data ......
Read more >Documentation Archive - Apple Developer
Title Resource Type Technology Date
Xcode Release Notes Release Notes 2018‑06...
Apple File System Guide Guides 2018‑06...
Understanding and Detecting OpenGL Functionality Technical Notes OpenGL 2018‑06......
Read more >image-webpack-loader - npm
Start using image-webpack-loader in your project by running `npm i ... Module build failed: Error: dyld: Library not loaded: ...
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
I ran into a similar problem with this module while using yarn autoclean. The ‘images’ submodule would be deleted after every install due to the ‘images’ entry in the default .yarnclean config. The issue was solved by simply removing the ‘images’ entry from the asset directories section.
@LittleMik thanks for following up with your findings, that is interesting.
We are big yarn users but not familiar with
.yarnclean
, and we have not run into this issue even though we make very extensive use of yarn.While we want things to work smoothly for everyone,I hesitate to rename a module just because of this, unless it is a bigger issue than I realize.
At first blush, it would seem like a yarn issue - they shouldn’t wipe out modules that happen to have the same name as asset directories. I would suggest opening an issue there and reference this ticket.