When the page loads at end of process it is empty

[bassmanitram]

Process [from fresh clone with no changes] completes successfully and opens a tab in Chrome (or FF) - which is empty.

Console log from chrome attached

[scotty-p]

I can recreate this issue using ap-southeast-2 region

[brettstack]

I'll spin up a fresh instance and see if I can repro (and fix). This is the error that's causing the problem:

Link.js:72Uncaught TypeError: Cannot read property 'createHref' of undefined

[brettstack]

Update ./dev-portal/package.json and change "react-router-dom": "^4.0.0-beta.4" to "react-router-dom": "4.0.0-beta.7".

From ./dev-portal run:

rm -rf node_modules
npm install
npm run start

After the final command kicks in, visit http://localhost:3000/ and verify it runs locally. Then, run npm run upload-site to deploy.

[brettstack]

Root cause: react-router-dom is in beta; API is in flux. Since we allow minor version changes (^), the API changes in newer versions of react-router-dom beta broke the app.

Solution: Remove ^ from react-router dom. In fact, to be safe, we will be removing it from all packages.

[bassmanitram]

Excellent - thanks - now onto a real API :)

[jose-rafael-marcano]

It didn't work for me

I had to add "react-router": "4.0.0-beta.7" in addition to current dependencies, but now I am not getting the sign in or register option. It is displaying Case Studies, APIs and Getting Started, but not register/login options. I am wondering if this is related to cache. Please @brettstack help out.

[jose-rafael-marcano]

I found the issue, it was a problem with my package.json. I had to add "react-router": "4.0.0-beta.7", in addition to "react-router-dom": "4.0.0-beta.7".
Thanks

[jessetarot]

@jose-rafael-marcano your solution of adding "react-router": "4.0.0-beta.7" to package.json
worked for me too. Thanks for posting.