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
Example: Improve ReasonML example #3021
Conversation
The lib folder contains code generated by BuckleScript, it shouldn't be versioned.
Next.js use case-sensitive-paths-webpack-plugin and BuckleScript tries to maintain the filename case.
This is the official recommended way in Next.js
Adds `"bsc-flags": ["-bs-super-errors"]` to the bsconfig.json file. https://reasonml.github.io/community/blog/#way-way-waaaay-nicer-error-messages
@mike-engel since you first pushed the initial example for ReasonML/ReactReason, I'd love to have your input on this. I'm just starting with ReasonML. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM
Thanks guys! |
With pleasure! |
please upgrade to reasonml 3 |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
This improve the example for ReasonML
with-reasonml
.While trying to run this example, I run into different issues, this PR is meant to fix them. While at it, this also upgrade some dependencies, including upgrading to next.js v3. And make some other improvements, enable nicer error msgs and update the example to use the new recommended
ReasonReact.reducerComponent
instead ofReasonReact.statefulComponent
- more read about this here.Note: I believe that the
package-lock.json
should be versioned in the examples, especially for theses kind of example which use "bleeding edge" stuff prone to break at any new deps update. However, #2623 ignore them, not sure why, so I didn't add the file.