Skip to content

Releases: wpdas/reactive-singleton

2.0.6

Choose a tag to compare

@wpdas wpdas released this 23 Oct 14:08
648fb40
  • package version

2.0.5

Choose a tag to compare

@wpdas wpdas released this 23 Oct 13:42
47bdb10
  • Dependabot updates

2.0.4

Choose a tag to compare

@wpdas wpdas released this 10 Mar 15:35
ff46209
  • A few modules were updated.

2.0.3

Choose a tag to compare

@wpdas wpdas released this 10 Mar 15:18
6680940
  • A few modules were updated.

2.0.2

Choose a tag to compare

@wpdas wpdas released this 19 Oct 20:17
66e73bb
  • Just a cosmetic update: Update Readme.md with the new version.

2.0.1

Choose a tag to compare

@wpdas wpdas released this 19 Oct 20:09
6aa865e
  • Updated important dependencies modules to improve security.

2.0.0

Choose a tag to compare

@wpdas wpdas released this 27 Aug 18:07
95347fe
  • SingletonProvider removed. This is no longer necessary due to changes in performance.

2.0.0-rc2

Choose a tag to compare

@wpdas wpdas released this 24 Aug 02:56
4a6aa84
  • Fixed the error message that was using an old resource reference

v2.0.0-rc1

Choose a tag to compare

@wpdas wpdas released this 23 Aug 06:16
55131be
  • Fixed the issue that was causing this error: React Error message before the version 2.0.0: React Hook "useWatcher" cannot be called in a class component. React Hooks must be called in a React function component or a custom React Hook function.
  • The main API resources provided by createSingleton() was using a resouce called useWatcher to be used inside the Singleton Classes, however this went against React Hooks rules. useWatcher was renamed to watch and the setValue was renamed to setClass. So that, the usage of createSingleton() should be used like:
const { watch, setClass } = createSingleton()
  • Fixed the issue that caused components to re-render more than necessary when using hooks
  • Added new hook: useReRenderOnUpdate
  • Added new HOC: withSingleton
  • New tests

1.1.7

Choose a tag to compare

@wpdas wpdas released this 20 Aug 04:35
e546a78
  • Fixed issue caused by multiple react-dom for ES6