Repl not loading sanctuary and ramda-fantasy

[apollux]

The Repl at https://ramdajs.com/repl/ tries to load sanctuary@latest and ramda-fantasy@latest, both redirect to a specific version and then result in 500 and 503 responses.

The requests:
https://bundle.run/sanctuary@latest -> 302
https://bundle.run/ramda-fantasy@latest -> 302
https://bundle.run/ramda-fantasy@0.8.0 -> 503
https://bundle.run/sanctuary@3.0.0 -> 500

I wanted to play around with Maybe and Either that is when I noticed something was wrong.

[CrossEye]

Hmm. It looks like bundle.run is having some issues. Does anyone have a preferred alternative we might try?

[apollux]

You could give unpkg a try: https://unpkg.com/ Have used it in the past, and worked well.

[CrossEye]

It looks like bundle.run fixed their issues. At least I can use Maybe in the REPL again. We'll try to keep an eye on this.

I'm not sure if unpkg will be helpful, looking at the differences between https://bundle.run/ramda-fantasy@0.8.0 and https://unpkg.com/ramda-fantasy@0.8.0.

[juboba]

This is still happening.
Browsing: https://bundle.run/ramda-fantasy@0.8.0
Gives me the error: "package has no entry file; please specify a module key in your package.json."

[CrossEye]

OK. I guess we're going to have to figure this one out. I'll try to look into it this evening.

[juboba]

Hey, just created a pull request for this.

[CrossEye]

Thank you @jujoba: That seems to have fixed it, at least after a hard refresh.

[juboba]

I just checked and it seems there's a problem with the modules 😭

[CrossEye]

@jujoba: You're right. I'd only checked that it loaded properly. Hmmm.

[customcommander]

@CrossEye Would it make sense to transfer this issue?

[CrossEye]

@customcommander: transfer it to where?

[customcommander]

@CrossEye Either to the repl repo or to the documentation repo?