Using magicbell with Deno and their Fresh framework

[MaDsEm88]

Have anyone had succes with adding magicbell into a Deno project?? . I am currently in the process of building a project inside the Fresh framework, but having issue getting the packages to work properly, have tried both the javascript and react package solutions...

Thanks again

[smeijer]

Hi @MaDsEm88 ,

I don't have experience with Deno, but I'm happy to look into it. Do you have any more info on what doesn't work? Is there an error message / stack that you're able to share?

[MaDsEm88]

@smeijer , that would be awesome if you have the time. Could probably make it work in time, but as I have other things i also need to figure out, so it would be nice to just be able to implement it without issues.. ;)

But have created the files one with react and one with javascript where the errors has been described. When using deno and especially the fresh framework, all of us using it loves the structure but because it runs without the use of node_modules we have to implement packages and solution in other ways..

And thanks again....

[smeijer]

The one using @magicbell/embeddable is due to server-side rendering. That SDK does not support server-side rendering, so you'd need to opt out of that for this one component.

For the react SDK, I'm not sure why, but esm.sh seems to load https://esm.sh/v135/[email protected]/denonext/headers.js instead of https://esm.sh/v135/[email protected]/denonext/dist/headers.js (note the dist folder). Do you know why it would do that?

[MaDsEm88]

No idea why it would show that. Normally when we wrap the react package it will show if we need to add further packages to make it work or we can force it to show by using the * before we type the package name like "https://esm.sh/133/*packagename", that will show if the package is using other underlying packages that also needs to be wrapped., so have no idea why it would show https://esm.sh/v135/[email protected]/denonext/headers.js