-
Notifications
You must be signed in to change notification settings - Fork 8
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
What templates should we provide? #11
Comments
I'd like to have a script that would integrate ReScript into an existing project.
|
Yes, that would be nice. Maybe we could add that as an option in create-rescript-app. Although people probably wouldn't expect this / wouldn't be looking for this functionality in a create-xxx package? 🤔 |
Yeah, probably, more obvious to have such behavior in the |
Things that come to mind:
|
I'm writing an article how to use ReScript for a CLI. Can be packed in a template repo. |
@cknitt What do you think of |
@zth I would also like to have a Vite template. There is https://github.com/jihchi/vitejs-template-react-rescript, but that one already includes a bit too much stuff IMHO (rescript-webapi, rescript-vitest). I would like to have a very simple template with only Vite - or maybe Vite + Tailwind CSS, that's a very nice combo that we are using in our projects. |
Regarding express vs. fastify vs. platformatic: I am currently seeing the following weekly download numbers on npm:
I think we should provide a template for express first because it still seems to be the most popular web framework for Node.js. Having a fastify template in addition might also be nice. I would not do one for platformatic. |
I would welcome a "rescript-development-testing" template that somehow comes with the latest master or at least the |
@DZakh Sorry for the late reply! Yes, it will definitely be nice to have a means to integrate ReScript into an existing project like you described. I am still a bit unsure about where we'd best put that functionality, but it will surely be helpful if you get the ball rolling with a separate |
Currently (as of v1.4.0) providing these two:
What other templates could/should we provide (while not going overboard with this and still keeping things minimalistic)?
How/where should the templates be stored to enforce consistency and avoid breakage?
Should we provide "experimental" templates for trying out things like JSX4?
The text was updated successfully, but these errors were encountered: