New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False Missing Export on export * from #3928
Comments
Looks like this issue: #3894 (note that cross-fetch is commonjs) |
It is not merged because there was no agreement yet how to handle multiple namespace reexports from files with synthetic named exports (i.e. commonjs files). |
@lukastaegert Sure does. I didn't connect the dots there. Is there a "better than nothing" path that we can take (maybe with warnings) that's better than no path at all? Without a path forward, I'm not sure how to get this bundle working aside from requesting changes from the package author. |
Expected Behavior
I'm attempting to bundle
@graphql-mesh/utils
which performs this import: https://github.com/Urigo/graphql-mesh/blob/4303d22a27690b0d0df6d4804aac2d233c6856a1/packages/utils/src/read-file-or-url.ts#L1From the the
fetchache
package: https://github.com/ardatan/fetchache/blob/09f0d39fe8a3e5f7d76e60dfe8aed08b77badfd8/src/index.ts#L63The
index.esm.js
file checks out, as it does anexport * from 'cross-fetch'
. That should work well.Actual Behavior
With both
commonjs
andnode-resolve
plugins, we get:Which is not true, as
Request
is actually exported viaexport * from 'cross-fetch'
. I downloaded the package tarball to confirm, and the same can be seen by inspecting the file in node_modules.Commenting out
commonjs
yields:Which is even weirder. There's definitely something funky going on with either module resolution, or Rollup not picking up on exports that are there.
The text was updated successfully, but these errors were encountered: