Closed lionel87 closed 3 years ago
found my mistake. my bad, sorry. it should be a dev-dep as it is. my configuration tricked me.
have the same issue
❯ node -v
v14.15.5
❯ npm -v
6.14.11
The only way that should happen is if your build step is messing up and including ./index.js
instead of respecting the main
entry point in the package.json
:
The only way that should happen is if your build step is messing up and including
./index.js
instead of respecting themain
entry point in thepackage.json
:
This can potentially happen when using esm
But I was unable to reproduce the bug. My steps were like this:
npm i is-mergeable-object
- after that everything workednpm uni is-mergeable-object
- after that, it still worked :/
When I try to require your package I get an
Error: Cannot find module 'is-mergeable-object'
message.\ Is there any reason theis-mergeable-object
package is included in the dev dependencies in yourpackage.json
?