You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2020. It is now read-only.
Hi, I've updated my project to the latest release candidate of Angular 6 and Angular cli 6 but this breaking change: angular/angular-cli#9827 (comment)
is causing AWS Cognito library to fail
The problem with net/global is not so straightforward. We are removing it for 6.x, yes (#9812). And we do expect this to cause problems to some projects. But we're not doing it because we want to break projects, we're doing it because leaving it in also breaks other projects, and it is incorrect.
The incorrect part is libraries that are meant to run in the browser relying on node globals being available. Browser code runs in the browser, not in node, and shouldn't expect things that are not available in a browser context to be there.
So when you serve an Angular 6 project with AWS Cognito you are getting an error "Uncaught ReferenceError: global is not defined" in Buffer.js
The text was updated successfully, but these errors were encountered:
Hi, I've updated my project to the latest release candidate of Angular 6 and Angular cli 6 but this breaking change: angular/angular-cli#9827 (comment)
is causing AWS Cognito library to fail
So when you serve an Angular 6 project with AWS Cognito you are getting an error "Uncaught ReferenceError: global is not defined" in Buffer.js
The text was updated successfully, but these errors were encountered: