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.

buildRegistry in ModuleLoader doesn't handle case of immediate node_modules

See original GitHub issue

E.g. if an input is node_modules/left-pad/index.js that never hits the split for /node_modules/ and thus isn’t subject to the resolve algorithm.

CC @ChadKillingsworth

Issue Analytics

State:
Created 7 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

3reactions

ChadKillingsworthcommented, Nov 29, 2016

That PR is the culmination of a year’s work.

0reactions

ChadKillingsworthcommented, Jan 28, 2017

Closed by #2130

Top Results From Across the Web

Webpack not excluding node_modules - Stack Overflow

From your config file, it seems like you're only excluding node_modules from being parsed with babel-loader , but not from being bundled.

`ts-node` fails when ES Modules are in the dependency graph ...

If we use module: 'commonjs' , then if any TS files import ES Modules (indirectly in their dependency graph), then Node throws an...

How to transpile ES modules with webpack and Node.js

Learn how webpack interacts with and supports ES modules in this deep dive tutorial on transpilation in Node.js.

Node Modules at War: Why CommonJS and ES ... - Code Red

The ESM module loader then asynchronously downloads and parses any scripts that you imported, and then scripts that your scripts imported, ...

A Guide to Managing Webpack Dependencies - Toptal

js, one of today's most popular JavaScript frameworks, module bundlers allow loading NPM modules in web browsers, and component-oriented libraries (like React) ...