You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The packages in that build can be installed and work in an npm project. However, the actual sandbox fork says the module is missing. When I look into the sources, I don't see @apollo/explorer anywhere in the node_modules like I'd expect. Here's a screenshot of what I'm looking at:
In the original sandbox, the @apollo/explorer module does show up in the node_modules.
Hopefully that's helpful, let me know if you need any more info from us.
The text was updated successfully, but these errors were encountered:
But when looking in the dist folder, I don't see it:
I think that this is giving the holdup, but we should have a better error message for this. I also don't know why we don't get this error when loading the sandbox, it could be because we're resolving a bit differently, but that's something we need to double check.
Thanks Ives, good find! We'll take a look and report back, hopefully I can just close out the issue (unless you'd like it left open as an action item for error messaging?). cc @mayakoneval
We're trying to use CS:CI for a React component for the first time and running into an interesting error that maybe y'all can help with.
Here's the base sandbox which is working fine:
https://codesandbox.io/s/npm-embeddable-explorer-zotwkv
Here's a PR which uses that sandbox in its sandbox config:
apollographql/embeddable-explorer#31
The packages in that build can be installed and work in an npm project. However, the actual sandbox fork says the module is missing. When I look into the sources, I don't see @apollo/explorer anywhere in the node_modules like I'd expect. Here's a screenshot of what I'm looking at:
In the original sandbox, the @apollo/explorer module does show up in the node_modules.
Hopefully that's helpful, let me know if you need any more info from us.
The text was updated successfully, but these errors were encountered: