Context with store has been broken since 6.0.0

import React, { Component } from 'react';
import ReactDOM from 'react-dom';
import PropTypes from 'prop-types';
import { createStore } from 'redux';
import { connect, Provider } from 'react-redux';

const store = createStore(
  (state) => state,
  { key: 'value' },
);

class App extends Component {
  static contextTypes = {
    store: PropTypes.object.isRequired,
  };

  constructor(props, context) {
    super(props, context)
    console.log(context)
  }

  render() {
    return null
  }
}

const CApp = connect()(App);

ReactDOM.render(
  <Provider store={store}>
    <CApp />
  </Provider>,
  document.getElementById('root')
);

I think this code is legal for any react and redux versions, but it is limited to react-redux v5.x only. react-redux >= v6.0.0 is not able to provide store, it is always undefined.

[andrew-aladev]

@timdorr Sorry, you can’t understand what i am talking about.

The only one legal (and possible) way to receive store in v5.x was store from context. This method has been clearly documented in v5.x.

The <Provider /> makes the Redux store available to any nested components that have been wrapped in the connect() function.

Note: If you really need to, you can manually pass store as a prop to a connected component, but we only recommend to do this for stubbing store in unit tests, or in non-fully-React codebases. Normally, you should just use <Provider>.

Today you are trying to say that first sentence about Redux store available to any nested components never existed, store was not available in nested components and authors of react-redux removed just internal functionality. It means that all packages and applications depends on react-redux v5.x and tries to access store has been broken by design.

Guys, if you are reading this issue, please try to avoid react-redux dependency in your applications. Authors of this package are not going to provide public api, they may always consider it as internal api and remove it without any notice (like deprecated).

[markerikson]

Oh, one other side note since I just re-read the original post here:

Yes, React-Redux v6 did drop the ability to pass store as a prop to connected components, but we brought that back in v7. That said, your original code snippet did not show that - you were mixing that up with passing store to <Provider>, which has always been supported.

You should really take the time to read my post The History and Implementation of React-Redux, which explains exactly why we’ve changed the implementation over time, and how.