Failing to install npm dependencies when using self-hosted bundlerURL about sandpack-bundler

[danilowoz]

@DeMoorJasper could you please take a look at this issue?

[zaini]

Any updates on this? I tried it on another PC and still get the same errors. It's a bit odd since some libraries work with the locally hosted bundler whereas others don't.

And all libraries work fine when using the CDN bundler. So it's almost like the locally hosted bundler is not the same as the CDN one.

Is there another bundler that can be used in the same way and is compatible with Sandpack?

[DeMoorJasper]

It should be identical to using: https://sandpack-bundler.pages.dev/ as bundlerUrl. You're probably comparing it to the v1 bundler which is still the default for sandpack, for which the sourcecode is here: https://github.com/codesandbox/codesandbox-client

[zaini]

If I change the bundlerUrl from my locally hosted bundler (https://github.com/codesandbox/sandpack-bundler), to https://sandpack-bundler.pages.dev/ I still get the same error. The only thing that works is not defining bundlerUrl so that it uses the default CDN bundler (which I don't want to use.)

[DeMoorJasper]

Yes, that's what I suspected, it's a bug in the new v2 bundler, you should probably follow this guide instead for self-hosting the v1 bundler: https://sandpack.codesandbox.io/docs/advanced-usage/client#hosting-the-bundler

[zaini]

How do I host the www file? I'm trying just npx http-server and then passing http://127.0.0.1:8080/ as the bundlerUrl but that doesn't seem to work.

Ideally I'm looking to only host the bundler. Is the bug with sandpack-bundler being tracked?

Thanks.

[KevinEdry]

Hey @DeMoorJasper, is this still an issue? I assume it is fixed by now.

[DeMoorJasper]

Don't think we've fixed this on the new experimental bundler, but it works on the stable bundler.

We're not yet sure how we're gonna fix this yet.