search

simov / slugify

Slugifies a string
MIT License
1.47k stars 126 forks source link

Cannot find module slugify (no valid entry point) from nested dependecies. v1.6.5 #149

Closed leonvanderstel closed 1 year ago

leonvanderstel commented 2 years ago

V1.6.5 doesn't have a slugify.js file, which breaks the dependency chain. In my case gatsby js breaks because it cannot find the slugify.js entry point

screen

Build error in my case gatsby js context screen2

When installing v1.6.4 within nested dependencies everything works and there is a slugify.js entry point.

screen3

Could you fix v1.6.5 so that everything dependant on it would keep working :)

simov commented 2 years ago

Not sure what may be the issue tbh.

Trott commented 2 years ago

V1.6.5 doesn't have a slugify.js file

Yes, it does. You are doing something else to cause it to not be there.

Trott commented 2 years ago

Could you fix v1.6.5 so that everything dependant on it would keep working :)

Trying to think what might be causing this, I suppose it's possible your npm cache is corrupted or something weird like that. But before looking for something like that, I'd completely remove your node_modules directory and try building again.

MooDySmiles commented 1 year ago

Had the same problem, confirm that deleting the node_modules solved the problem, though happened only with this library and not with other 🤷🏼