-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Change msal-angular to output es5, fixing compatibility with IE11 #868
Conversation
38022d3
to
950643d
Compare
will this effect any who are using es6 modules / any other side effects? |
I suppose it might impact es modules in theory, but I'm not sure if anyone uses es modules with Angular in a way that would break (or if that's even possible?). |
looks like tests are failing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also push the dist files or add them to gitignore like core and remove them now?
@sameerag Yeah we can probably remove the dist files from the repo. |
7d50f19
to
cc29159
Compare
79063f6
to
13d1c5a
Compare
13d1c5a
to
2bcb57b
Compare
5aeeaf8
to
728c3ae
Compare
728c3ae
to
89524ab
Compare
…rary-for-js into angular-es5-ie11 # Conflicts: # .gitignore # lib/msal-angular/src/msal-guard.service.ts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might be winning the +/- battle on code here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. One comment but not a blocker.
Fixes MSAL Angular compatibility with IE11 by changing the output to
es5
.Key changes:
tsconfig.json
, and also changed the options accordingly.ngc
command.dist
folder from the repo.msal
core0.2.2
which introduced thestoreAuthStateInCookie
config flag for IE11.Once approved, I plan to release as a beta to ensure we haven't introduced any regression like we did last time.