Removing the ability to create a Redux store directly from the extension

It is possible to create a Redux store directly with the extension (without importing Redux in your app) when you need it for debugging only. It’s not about the store enhancer or compose helper as it’s usually applied. See the docs, the example and the blog post for more details. That was introduces for more than 2 years, but doesn’t seem anybody using it. Now with React hooks, that example wouldn’t make much sense. One can move that inside an integration including redux for development only, like reinspect does.

The suggestion is to remove that part in next major release. I’ll add a deprecation waring in the next minor version.

If you’re using it, please let me know about your use case.

[CharlesStover]

If this is still an issue, I am in the process of adding ReactN’s global state to Redux DevTools. Since ReactN does not use a Redux store, it is not possible to pass an existing one. Having the DevTools fallback to making one would be beneficial, such that the dependency lies in the extension instead of in my package. It is detrimental to my users to have them include Redux in their bundle just so that one of their developer tools can show them a store.

Without this feature, I am left having to make my own minimalist implementation of a store so as not to include Redux in my bundle. It’s been a burden to create, and will continue to be a burden to maintain. This would be alleviated if Redux DevTools made the store on its end.

As is, I’m currently afraid to rely on Redux DevTools creating the store, given this Issue and the comment about its deprecation(?).

But this is my use case. I do not want to maintain a Redux store, but I do want to display a non-Redux store to my users.

[nik72619c]

anybody working on this issue ?