-
Notifications
You must be signed in to change notification settings - Fork 23
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
Running Lesson 7.1 #25
Comments
Yeah I might have to re-record that lesson. The various beta and rc versions react-router changed dramatically. |
Instead of re-recording lessons, another option could be to make errata pages for each lesson and then add the same short recording to each video showing them the link to the errata pages. On the errata pages, you can then post what exact versions that you need for the tutorial to work and, if you have time, post solutions for the latest versions. |
I don't think re-recording is necessary. In any case the stuff changes so I attended a local tech camp http://becamp.org/schedule yesterday where You are welcome to post the file I sent you. Meanwhile I will try to On Sun, Oct 25, 2015 at 11:07 AM, Oliver Forral notifications@github.com
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we |
Two simple changes will allow this lesson to run:
public
directory is missing. You must make the directory. Leave it empty.package.json
, changing line Lesson 1.2 Setting Up Your Development environment #31 to force loadingreact-router 1.0.0-beta3
and only that version:"react-router": "1.0.0-beta3"
.I haven't found the magic for handling server rendering and routing with the newest version of
react-router
. It seems to have changed drastically. Maybe it can work with theRouter.run()
call inserver.js
(line #23) butLocation
no longer exists and I cannot gethistory/lib/createLocation
to work. In any case,react-router
locations may be changing and may well work some other way before it is finalized.The text was updated successfully, but these errors were encountered: