ReferenceError: initialState is not defined
See original GitHub issueI am sorry for this, actually there is no error with your boilerplate. Let me explain.
I have cloned your boilerplate to use for my Recipebook(the app i am building in educational purposes in order to get solid understanding of redux ecosystem).
So i have changed boilerplate to fit my needs.
After that i run npm run build
successfully.
And then i get error(screenshot below) on ‘npm start’.
I have created Recipebook repo where i have uploaded my code.
I know i asking for too much but i am eated my braines trying to figure this out.
Can you please check my repo and help me figure out how to fix this error.
Thanks in advance!
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
initialState undefined (Example) | Treehouse Community
Hi all, My Git shell is compiling the project in it's current state with npm start but there's a console error in the...
Read more >Uncaught ReferenceError: initialState is not defined
I'm getting this when trying to edit the home page only. It just shows a blank page with no elements in it. All...
Read more >Uncaught ReferenceError: state is not defined - Stack Overflow
Why are you using connect? Do you have a redux store? state is probably undefined because by default state will be undefined if...
Read more >useState is not defined ReferenceError in React [Solved]
The "Uncaught ReferenceError: useState is not defined" occurs when we use the useState hook in our code but forget to import it. To...
Read more >initialstate' is not defined no-undef Code Example
Answers related to “initialstate' is not defined no-undef” ... react modal error app.js:68486 Uncaught ReferenceError: useState is not defined at new App ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Quick Solution: This may not be the perfect solution but what i found it to be is way the node/test envs are reading the modules. replace const/let with var and replicate the object in param assignment.
It Works