Reflux.Store.state is inaccessible on v6.4.1

Hey guys. First of all sorry me if it’s stupid issue. I’m just going to migrate from native flux to reflux.

So, when I’m trying to create store, I have an error: “Reflux.Store.state is inaccessible before the store has been initialized.”

I can reproduce this bug only on v6.4.1. On 6.3.0, 5.0.4 - there is no problem.

Code is very simple:

const React = require('react');
const Reflux = require('reflux');

class MyStore extends Reflux.Store {
}

module.exports = MyStore;

I do something wrong?

[vladimir-konnov]

@micheltobon the issue cannot be closed, because the problem is still there. Every time one requires a store in a component class, he gets “Reflux.Store.state is inaccessible before the store has been initialized.” error in v.6.4.1. Please investigate and solve it (if you are on the reflux team). The examples provided above give you all the necessary information to do it.

[BryanGrezeszak]

Unfortunately I cannot get the examples given to reproduce the error.

For example, I did my best runnable interpretation of the gist that hololoev made at a jsfiddle here, but it works fine without any visible errors.

I believe you that you’re having the issue, but unfortunately we cannot fix that which we cannot reproduce. Code examples in the format of just describing “this file this code, that file that code” are actually not always super helpful, because that’s not runnable code, but rather a vague description of a project setup that doesn’t actually include a lot of the data about how the project is set up (e.g. how is the JSX being transpiled? Is it running node or are those requires being transpiled together? if so via what system? what versions of each lib involved are being used? …sometimes the issue lies in those details). Sometimes that type of description is enough…but sometimes it’s not.

In some cases the person with the problem truly is the only person that can make a viable running example of the problem…so we need you to do that. That means either something like a codepen/jsfiddle that actually causes the errors, or if too complex for that then a legit example project of the error that can be pulled/npm install/npm start type thing. Sometimes that’s the only way to actually get the developers to be able to reproduce your problem, and this seems to be one of those times because I’m doing as accurate of interpretations of the code you’re posting as I can, and the error is simply not coming up in them.

So I’m closing this, simply because it’s old anyway and already includes a bunch of posts that haven’t gotten us closer, so if we’re gonna fix it we might as well doing it as a fresh issue with repeatable examples of the error when the time comes. So if we can get a viable reproduction of the error then I welcome it being posted as a new issue.