Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: rescript-lang/rescript-react
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.13.1
Choose a base ref
...
head repository: rescript-lang/rescript-react
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
  • 7 commits
  • 31 files changed
  • 4 contributors

Commits on Mar 5, 2025

  1. Remove v3 legacy modules

    cknitt committed Mar 5, 2025
    Configuration menu
    Copy the full SHA
    c73c9be View commit details
    Browse the repository at this point in the history
  2. Remove deprecated stuff

    cknitt committed Mar 5, 2025
    Configuration menu
    Copy the full SHA
    72f75cc View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    2f7a5fa View commit details
    Browse the repository at this point in the history

Commits on May 4, 2025

  1. React 19 APIs (#133)

    * React.promise
    
    * React.useTransition
    
    * React.useActionState
    
    * React.useOptimistic
    
    * React.use
    
    * React.act
    
    * React.useDeferredValue now takes initial value
    
    * ReactDOM: ref cleanup function
    
    * ReactDOM: Resource Preloading APIse
    
    * ReactDOM.useFormStatus
    
    * JS output changes
    
    * Add external for basic support for formAction
    
    * Add `usePromise` for `use(promise)`
    
    `use(context)` seems to exactly replicate the `useContext(context)`
    logic, and we want to maximize retro-compability (ie. not switch from
    `useContext` to `use` for that under the hood).
    
    simply adding `usePromise(promise)` seems to be the simplest, least
    invasive way to add the functionality.
    
    * proposal: make FormData more usable to get values
    
    this **kinda** goes against the zero-cost philosophy, but I don't see a
    world where users would not have to reimplement those.
    
    * useOptimistic optionnal updateFn
    
    * dom static prerender and prerenderToNodeStream
    
    ---------
    
    Co-authored-by: Matthias Le Brun <bloodyowl@icloud.com>
    Co-authored-by: Freddy Harris <freddy03h@gmail.com>
    3 people authored May 4, 2025
    Configuration menu
    Copy the full SHA
    78c2fcb View commit details
    Browse the repository at this point in the history
  2. Version 0.14.0-rc.1, update README (#139)

    * Version 0.14.0-rc.1
    
    * Update README
    
    * Bump react dev/peer dependencies to 19
    cknitt authored May 4, 2025
    Configuration menu
    Copy the full SHA
    caed8c9 View commit details
    Browse the repository at this point in the history
  3. Update CHANGELOG (#140)

    cknitt authored May 4, 2025
    Configuration menu
    Copy the full SHA
    a59d15d View commit details
    Browse the repository at this point in the history

Commits on Jun 4, 2025

  1. Configuration menu
    Copy the full SHA
    056ce1c View commit details
    Browse the repository at this point in the history
Loading