I've been playing around with Razzle and how the Server HMR works.

I generated a Razzle Project and run it

• npx create-razzle-app my-app
• cd my-app && yarn start

If I now edit the src/Home.js I see hot reloading working in the browser and I see the server.js being re-required by the index.js. But if I open my dev tools "view page source" my changes are not actually in the HTML

This is probably related to if not identical to #1687, but we at least need a better error message.

https://reasonml.github.io/try?reason=M4dwlgLgxgFgFARgNQIJQAIDeAod6A+6ATOgLwB86cqu6A9AFS0CGAJq+swHboCmAHhABOzdA3QQA9hJi90wCMyER0kgGYywwdFEkBbPby4QANPOmR0AI167D2hkzwM6tQgH0ylatgC+QA

switch(1+1) {
  | 2 => ()
  /*
  works
  */
  | _ => ()
}

switch(1+1) {
  | 2 => ()
  /

I cloned and built revery-quick-start and started looking through App.re to see how it all works. I noticed it opens Revery.UI but there didn't seem to be any documentation for things like Opacity and View on https://www.outrunlabs.com/revery/api/revery/. Poking around I managed to guess the URL and found them at https://www.outrunlabs.com/revery/api/revery/revery_ui/ and https://www.out

Since we don't have an interactive tutorial, and our docs are sparse, we should at least be bundling the existing vim tutor.

• Include the vimtutor as a runtime asset.
• Add a command to open the vimtutor
• Set the readonly flag on vimtutor, so that it can't be saved.

Additional things to think about:

• We should hook up a Vim command as an entry point as well (ie, :tutor, `:vim

A lot of folks have been asking about a documented ReasonReact API

• mentioning stuff that's going away / deprecated
• going through the API and at a high level, talking about each function.

There are curried versions of that function, but we should talk about them under each top level, for example:

• useEffect
  talk about useEffect0, useEffect1, etc, here
• useState

There is no mention of the --fish option in the README and its functionality is encapsulated by the --shell option, but --fish is still documented in the manpage and still works.

Currently It's really cumbersome to discover how to tweak the KLISPE APP.
There are a couple of hotkeys and url parameters documented here: http://blog.klipse.tech/clojure/2016/03/27/klipse-manual.html

Here are a couple of ideas - given by @pesterhazy how to do that:

• Like github.com narrow top bar
• Like reddit.com tab-like rider
• Like this

Lot of packages depend on bs-react-native, such as this. We'll need to work with these package owners to migrate to the next release of reason-react-native.

Preliminary list from npm search:

• [x]

When loading the website via Safari 12.0 (13606.2.11), the same icon for the 💬 bubble is requested repeatedly.

So Docusaurus is amazing for building sites and documentation and I really want to use it. It would be awesome to also port over the current homepage to a custom React component that can be used on the homepage too.

As marked in https://github.com/briskml/brisk/blob/master/examples/hacker-news/app/Story.re#L82, we'll need to transform incoming html.

<p> tags are not rendered with proper margin/padding by Cocoa in NSTextView by default, and instead of manually changing document attributes on ObjC bindings side, simply pre-processing html text and replacing paragraphs by newline characters seems more prefe

The current react tutorial uses Apollo Client v2 stable. v3 changes some of the APIs. We can update the tutorial with the necessary changes.

• cache.read and cache.write are replaced with cache.modify.

// TODO: Add more changes here.

Relevant issue: jsdelivr/jsdelivr#18166

Update

So apparently jsdelivr will minify the main entry file and add .min. in its name. Since we check for the name. And the minified file could saves a lot of bytes and improve parsing speed for the bundler.

So we would save this default file provided by jsdelivr, check with what's provided in main field

According to reason-react docs instance variables should be stored in state and be marked with ref instead of mutable to prepare for concurrent react.

I am unsure whether this makes any difference for a global state management solution like reductive, but would be nice to have a better insight into thi

Similar to OCaml documentation - lets do https://realworldocaml.org/ automatically so that learning Reason is painless.

Right now those gifs are using old Reason syntax. It would be great to update them to the latest syntax 🙂

It would be great to have a couple of example apps, similar to Redux and co. inside an examples folder in the repo.