-
Notifications
You must be signed in to change notification settings - Fork 72
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
Consider use of unpkg CDN for REPL libraries #162
Comments
what wzrd gives up is "browserify as a service" which i believe is required to serve up RF and S which are not bundled for the browser |
Given the benefits of having a browser version in the package, would it be worthwhile adding these to Ramda Fantasy? I hope @davidchambers doesn't mind me pinging him on his thoughts of adding it to Sanctuary. |
Actually, Sanctuary should run in the browser. |
So it would be possible to serve it up with unpkg? |
Yes. I just confirmed that this works: <script src="https://unpkg.com/[email protected]/dist/ramda.js"></script>
<script src="https://unpkg.com/[email protected]/index.js"></script>
<script src="https://unpkg.com/[email protected]/index.js"></script> Keep in mind that the Sanctuary module is exported as |
in that case we could either bundle RF for the browser or just use S. either is fine with me |
Quickest fix would seem to be adding a Rebinding variables for the REPL would be a useful option. I haven't looked at the Ramda Fantasy code at all, but I could have a go at hooking up that script if people are keen. |
@MattMS you can reuse or supercede this |
@buzzdecafe (if I'm not mistaken) it seems that PR only needs the In that case, would it be easier for you to make that change? |
Since there have been reliability issues with the REPL libraries in the past, would it be worthwhile switching over to unpkg?
It has a latest version redirect as well as allowing specific versions.
My understanding of the currently used wzrd.in service is that it performs extra steps to bundle the code, but since the code is already bundled in the repo, maybe it would be quicker to use a straight CDN.
The text was updated successfully, but these errors were encountered: