How do I debug this? Package exists but package.json “exports” does not include entry for ... #3871
Replies: 2 comments
-
console.logging was no use, but grepping node_modules did the trick!
Still curious about debugging options as this isn't ideal, so I'll leave it open for now. |
Beta Was this translation helpful? Give feedback.
-
The library that triggered the error uses commonjs like this: require('ramda/src/forEach') (The error being caused by ramda/src/reject in the previous post was due to me messing with pkg.exports for ramda to debug the issue) which is perfectly valid with commonjs resolution. I added this to solve the problem: import { nodeResolve } from '@rollup/plugin-node-resolve'
export default {
// ...
packageOptions: {
rollup: {
plugins: [nodeResolve()],
},
},
// ...
} That did not work, so I'm still not sure how to solve the problem. This would have been a nicer error to debug.
|
Beta Was this translation helpful? Give feedback.
-
I've started migrating a large application to Snowpack, but I am stuck at this message:
The issue is that, while this is a valid error indeed, I have no idea how to debug it. The docs do not show how to debug this and I tried running
DEBUG=snowpack snowpack dev
to no avail.My next debugging effort would be to sprinkle console.log around in node_modules, which is not ideal.
Got any tips?
Beta Was this translation helpful? Give feedback.
All reactions