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.

1.2.4 breaks webpack compilation

See original GitHub issue

Module '"D:/xxx/node_modules/slugify/index"' resolves to a non-module entity and cannot be imported using this construct.

Issue Analytics

State:
Created 6 years ago
Comments:9 (7 by maintainers)

Top GitHub Comments

1reaction

neonerdcommented, Nov 24, 2017

You have a pull request fixing this, tested with newest Webpack / TS-Loader example.

Works both with

import slugify from "slugify"

and

import * as slugify from "slugify"

now.

1reaction

neonerdcommented, Nov 15, 2017

I’m not sure whether it was 1.2.4 or something before, the last working version was 1.2.1 for me.

I’ll try to attach a reproducable setup tomorrow. 😃

Top Results From Across the Web

Core module changes break compilation · Issue #4353 - GitHub

The app compiles successfully when running ng serve . Changes to any files outside of the core module cause the app to recompile,...

Webpack suddenly broke - Stack Overflow

But I think ts-lint is just crashing on wrong input (something else in a chain broke it earlier). I am pretty sure I...

Webpack / babel / asset compilation is broken when FIPS ...

This breaks all forms of asset compilation and serving in GDK, making it difficult to investigate further FIPS-related issues in the ...

Upgrading jq-pro 4.7.7 to 4.8 broke my webpack - MDBootstrap

I simply ran a yarn upgrade. Now when I try to compile I get. ERROR Failed to compile with 1 errors 9:36:29 AM....

Experiments | webpack

Because experimental features have relaxed semantic versioning and might contain breaking changes, make sure to fix webpack's version to minor e.g. webpack: ...