-
Notifications
You must be signed in to change notification settings - Fork 94
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
Chapter 02 - React doesn't take effect page 22 #21
Comments
I ran into this same issue and it came down to changes made in babelify v7 from v6. So, you can fix it by either using babelify 6.2.0 as in the git repo here, or you can run:
And modify this line in your gulpfile:
To be this:
...and you should then be good to go on the v7 release of babelify. |
@blitzd thanks! I just verified that this fixes the issue. |
@blitzd, thanks for the tip! |
@blitzd thanks for supporting your fellow readers! |
Works for me. Thanks! |
v7 will require something similar to get the later (jsx) tests working as well. I added a .babelrc file for this with:
to get the jsx in the test specs to work correctly. |
@blitzd Thank you kindly for the fix sir! Good Karma for you! |
thanks, it worked! |
@blitzd Thank you for the tip! |
I run into problem on page 22. It says the html page should be empty and I should open developer tools to find an empty h1-tag. My page is not empty and shows the original text ("I am about to learn the essentials of React.js.") from the index.html file. It hasn't been written over by app.js or anything.
If I run the downloaded code it works fine and shows three list items instead of the original text but I haven't gotten to the end yet. So I tried to copy the code from the example files (except for app.js and snapterest.js) and build again with gulp. I still get the same result. Gulp finishes and I can see the snapterest file is updated. The only difference I can find now is in the versions of babelify and browserify in packages.json. I tried changing them as well and build again. Still no change.
So React doesn't even kick in....
The text was updated successfully, but these errors were encountered: