Unfortunately, the biggest problem with JSX in Rescript is when your components have to operate on `data-attributes` available in HTML. Using data-attributes in Rescript is a nightmare, and it shouldn't be!
I think this is improved in 11.1 forum.rescript-lang.org/t/custom-data-attributes-in-jsx/5157 You're right that the NextJS bindings aren't complete. I think the intent was to have something to get you started with an expectation that you'll have to do some bindings yourself. As the community grows, it'd be great to see bindings improve for major JS projects like NextJS.
There are really few developers on YT recording about Rescript, and those who do always avoid developing Rescript applications with Next.js 14, because there is absolutely no API in Rescript ready to use with the new Next.js based `app router`. Providing Next.js options in the Rescript CLI is a messy lie.
Unfortunately, the biggest problem with JSX in Rescript is when your components have to operate on `data-attributes` available in HTML. Using data-attributes in Rescript is a nightmare, and it shouldn't be!
I think this is improved in 11.1 forum.rescript-lang.org/t/custom-data-attributes-in-jsx/5157 You're right that the NextJS bindings aren't complete. I think the intent was to have something to get you started with an expectation that you'll have to do some bindings yourself. As the community grows, it'd be great to see bindings improve for major JS projects like NextJS.
There are really few developers on YT recording about Rescript, and those who do always avoid developing Rescript applications with Next.js 14, because there is absolutely no API in Rescript ready to use with the new Next.js based `app router`. Providing Next.js options in the Rescript CLI is a messy lie.