-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redux.creatStore is not a function #296
Comments
I can't see in the external resources that you import Here is a Basic Codepen example that you can start to play with. Does this help? |
@moroshko why use redux internally? Wouldn't it be better to allow the app itself to handle state rather than implicitly forcing a new redux store? Seems kinda hacky :( |
I am also having this issue :( |
I am having the same issue. Is there anyone figuring out how to get rid of this? |
@superliuwr Could you help creating a minimal Codepen that reproduces the issue? |
@moroshko I tried putting just the component itself into a Codepen and it didn't reproduce the issue. It appears something to do with either Redux or my webpack config. There is a file named redux.js in your source code which I suspect causing name resolving issue of Redux. I however can not prove it at the moment. |
It seems the error occurs when a redux store has already been instantiated, but then this library attempts to create another one. Babel/webpack parsing error perhaps? |
@moroshko this is a simple demo that reproduces the bug |
I know I'm late to the party, but can anyone actually provide a solid example of the failings of this? I have autosuggest working flawlessly in a massive react-redux app. The above demo appears broken. |
Hi, Example here https://github.com/craigcosmo/demo You are right, I forgot to save-dev some dependencies when npm. It's fixed now |
@adack123 I updated the demo, fix the broken dependencies |
Hey @craigcosmo Sorry to be the bearer of bad news but I just tried out the demo and I'm still getting a lot of webpack related thrown errors revolving around sass and image files. |
@adack123 I know why, the image folder was empty, therefore it was not pushed to git. But the build require the image folder so it complains. I made the fix. please have a look again |
@adack123 have you tested out the reproduction repo I posted? |
Could you please upgrade and verify that the issue is gone? |
updated to v8, I got this error reproducing https://github.com/craigcosmo/demo |
@craigcosmo You have to add: this.onChange = this.onChange.bind(this); in your constructor, or alternatively, write onChange = (event, { newValue, method }) => {
this.setState({
value: newValue
})
}; (do the same for |
Hi,
I just install the latest version. Then copied the code from basic sample and make a component (compoent Auto) with that code. Then I import Auto into my project. Run, then I got this error
Here is the code for Auto of component https://jsfiddle.net/craigcosmo/ju43d66a/
The text was updated successfully, but these errors were encountered: