Skip to content
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.

Sign up for GitHub

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

Jump to bottom

improve dev experience #4

Open
jedwards1211 opened this issue Jan 14, 2017 · 0 comments
Open

improve dev experience #4

jedwards1211 opened this issue Jan 14, 2017 · 0 comments
Labels
enhancement

Comments

@jedwards1211
Copy link
Member

debugging issues with combineReducers etc. can be tricky because it's not immediately obvious where the problematic reducer was created. I need to figure out the best way to ease debugging in this case. One idea is to store a stack trace when combineReducers etc. is called (as long as process.env.NODE_ENV !== 'production', and if applying the reducer throws an error, include the creation stack trace in that error somehow.
jedwards1211 added a commit that referenced this issue May 29, 2018
@jedwards1211
Merge pull request #4 from jedwards1211/greenkeeper/babel-plugin-ista…
0a71382 
…nbul-4.0.0

Update babel-plugin-istanbul to the latest version 🚀
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jedwards1211