Skip to content

ReScript support #159

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

Open
Zizico2 opened this issue Feb 21, 2021 · 3 comments
Open

ReScript support #159

Zizico2 opened this issue Feb 21, 2021 · 3 comments
Labels
∆ feature New feature 🅝 npm package NPM package support
Milestone

Comments

@Zizico2
Copy link

Zizico2 commented Feb 21, 2021

Are there any plans to support any other languages like ReScript?
Could we have ReScript as a an officially supported language? React bindings already exist and Aleph bindings shouldn't be too hard to muster up.

@shadowtime2000 shadowtime2000 added this to the future milestone Feb 21, 2021
@shadowtime2000 shadowtime2000 added ∆ feature New feature 🅝 npm package NPM package support labels Feb 21, 2021
@shadowtime2000
Copy link
Member

I have never used ReScript so idk most of the stuff.

But it seems like ReScript requires an NPM package?

This would be a very large feature and would probably require Deno support from ReScript.

@Zizico2
Copy link
Author

Zizico2 commented Feb 21, 2021

Ah, that is true. I completely disregarded that we don't use npm here. I'll bring this fight to ReScript as well. Using ReScript is such a breath of fresh air. I've been avoiding JavaScript for as long as I've been developing for the web. TypeScript is good but it aims to be a superset of JavaScript which holds it back imo. I'm using nextjs+rescript for the website I am currently developing.

This could remain as a long term goal if ReScript eventually gets Deno support.

@shadowtime2000
Copy link
Member

@Zizico2 Once ReScript gets Deno support it would probably be simple to add support, we just need to write a plugin for our loader system then.

I have no idea how ReScript works but I think it is built on OCaml which I think is a native language so yeah, it may take more then creating an esm.sh url to use it in Deno.

If you create an issue there or something for Deno support it would be great if you could put the link here for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
∆ feature New feature 🅝 npm package NPM package support
Projects
None yet
Development

No branches or pull requests

2 participants