New polyfill to fix PubSub for SSR breaks checks for SSR.

[cgarvis]

Versions:
aws-amplify@0.2.15
next.js@5.0.1

What is the current behavior?
When using the latest amplify code with polyfill, it doesn't polyfill the window object fully so it breaks other SSR checks liked here: https://github.com/zeit/next.js/blob/085b2f806afd4d16e6f4754cce62e88d7bd47518/lib/router/router.js#L45-L50 which in getUrl is looking to the href on location which hasn't been polyfilled.

What is the expected behavior?
Set location to empty object.

[nidsharm]

Hi @cgarvis,

Thank you for reporting this bug. We will fix it soon.

[leonfs]

Encountered the same problem. @cgarvis Have you rolled back to a previous version? or you are still unable to use aws-amplify with nextjs SSR?

[michaelmerrill]

Also experiencing this issue with the latest versions of amplify and nextjs.

"aws-amplify": "0.3.3",
"aws-amplify-react": "0.1.43",
"next": "5.1.0",

Quick question. If amplify adds a location property with an empty object to the polyfill here, nextjs will still error due to href not being defined. What's the solution there? Is it something that amplify should handle or nextjs in the way they are getting the url here.

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.