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.

Fix webpack usage

See original GitHub issue

The npm package only bundles the built files under dist, but webpack doesn’t like the fact that there is a require for a lib dir that doesn’t exist.

This can be fixed by including lib but there should be a better way to make webpack not worry about this.

Issue Analytics

State:
Created 8 years ago
Comments:13 (9 by maintainers)

Top GitHub Comments

2reactions

Kodedcommented, Jan 11, 2017

Thanks for the quick response @Khaledgarbaya - good to hear you’re going to look into the problem.

1reaction

Kodedcommented, Jan 23, 2017

Hi @Khaledgarbaya

I’ve just checked out that PR branch and built and run it on my app and it all works as expected!

Top Results From Across the Web

Resolve | webpack

These options change how modules are resolved. Webpack provides reasonable defaults, but it is possible to change the resolving in detail.

A Guide to Managing Webpack Dependencies - Toptal

Configuring Aliases and Relative Paths ... Relative paths are not directly related to dependencies, but we use them when we define dependencies. If...

How I solved and debugged my Webpack issue through trial ...

When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.

node.js - how to fix the webpack when I use express

I use express and github actions and webpack. There is my code. Node version = v12.18.4. app.js const webpack = require(" ...

fqborges/webpack-fix-style-only-entries - GitHub

It just find js files from chunks of css only entries and remove the js file from the compilation. How to use. install...