Version 2.0

[danielkcz]

I think it's time to get this thing out. It seems that React 16.9 has included some preliminary changes for upcoming Concurrent mode which are causing trouble with the current test.

With the code of useObserver from next branch, tests are passing again although there is a bunch of act warnings which might be false positive as it's actually necessary to simulate commit phases and similar. We can review that later.

Personally, we have been using this branch for a couple of months now in production and no related problem seems to occur.

Changelog follows:

## Breaking changes:
 * Remove deprecated hooks `useComputed`, `useDisposable`, `useObservable`
 * Internals of `useObserver` are rewritten to support React Strict mode [#121] @RoystonS 
 * UMD bundle is moved to `mobxreactlite.umd.production.min.js` or `mobxreactlite.umd.development.js` respectively.
 * React Native no longer has a specific build, the regular one can be used

This branch has diverted from master fair amount and is really hard to rebase. For any further updates just merge master directly and we will squash later.

[coveralls]

Coverage decreased (-3.6%) to 95.098% when pulling 5655419 on next into d638b07 on master.

[xaviergonz]

LGTM, just I think that there could be an optimization in the cleanup code.
If instead of a plain list the reactions were sorted on insertion (with priority set to cleanup time, via for example via a heap structure), then instead of traversing the whole list you could traverse the list from "soonest to latest to be cleaned" and break as soon as the time is already "not to be cleaned"

[danielkcz]

@xaviergonz I am sure it can be improved later. Such internal optimization won't be a breaking change most likely. But feel free to submit a PR if you like.

[xaviergonz]

Btw, since it is now using tsdx I have the hunch .browserlistrc, tslint.config and jest config files are no longer needed

[xaviergonz]

And probably it might be worth to add a .eslintrc.js with

module.exports = {
    extends: ["react-app", "prettier/@typescript-eslint"]
}

if not in the package json already

[danielkcz]

Btw, since it is now using tsdx I have the hunch .browserlistrc, tslint.config and jest config files are no longer needed

TSDX is just a build tool, the Jest config is still needed for sure, the .browserlistrc not sure how is that utilized actually. TSLint still works, but yea, I want to replace it with ESLint eventually, not sure if straight in 2.0, will see.

[mweststrate]

Just checking in, was this waiting for something from my side? (Github notifications stopped working for me years ago)

[danielkcz]

@mweststrate No, I think this is mostly on me. I got kinda busy and forgot about this. Want to finish up #214 first and now also #226 should be figured out first.

[danielkcz]

Alright, almost ready for release, just waiting for confirmation if the fix for #226 works.

[mweststrate]

Given that the next branch solved some problems for others, I guess we can also cut a release and deal with any fallout later? I doubt we get more feedback without releasing.

[danielkcz]

@mweststrate Well, given the Concurrent is now available for the library authors, I think it would be responsible to test it out properly with it before going full 2.0. However, right now the @testing-library is lacking behind and it's not really possible to run tests with Concurrent mode enabled.

[MohamedLamineAllal]

The build for the last version npm install mobx-react-lite@next. Have a problem considering typescript. index.d.ts is missing!
The current version have no problem however!
A feedback. And thank you a lot.

[danielkcz]

Thanks a lot for the feedback, not sure how could that happen. Fixed in 2.0.0-alpha.4

[auvipy]

can you rebase it?

[danielkcz]

@auvipy Not before figuring out if there are some issues with the Concurrent mode.