Closed Crio1979 closed 1 year ago
Invalid Issue Template: Please update the original issue and make sure to fill out the entire issue template so we can better assist you.
Invalid Issue Template: Please update the original issue and make sure to fill out the entire issue template so we can better assist you.
This issue has not seen activity in 14 days. If your issue has not been resolved please leave a comment to keep this open. It will be closed in 7 days if it remains stale.
@Crio1979 Apologies for the delayed response. I am unable to reproduce this behavior using our Angular 11 sample: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/971e30f44c76b6c29546e80e69b3f881624808d8/samples/msal-angular-v2-samples/angular11-sample-app/tsconfig.json#L18
Are you able to reproduce this error with that sample? And if so, can you share details? Thanks!
@Crio1979 This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.
issue persists with Angular 9.1. with ngcc getting the following error:
target is es5
@tnorling
The project for reproducing the issue is here: ng9.zip
Node: v14.15.0 OS: Windows 10 x64
Note: if you change tsconfig.json target from "es5" to "es2015" and revert it to "es5" the issue will stop to reproduce. In this case you should remove node_modules
folder and make npm i
. Then the issue will start to reproduce again.
Also I can give you more details if you need.
From Russia with love.
@jasonnutter
@Crio1979 Apologies for the delayed response. I am unable to reproduce this behavior using our Angular 11 sample:
Are you able to reproduce this error with that sample? And if so, can you share details? Thanks!
I noticed that Angular 10 ignores "target": "es5"
option. I suppose it is same for Angular 11. Instead of compiling esm5
, Angular 10 compiles code to esm2015
.
Angular 10 output with "target": "es5"
:
Compiling @angular/core : es2015 as esm2015
Compiling @angular/common : es2015 as esm2015
Compiling @angular/platform-browser : es2015 as esm2015
Compiling @angular/router : es2015 as esm2015
Compiling @angular/platform-browser-dynamic : es2015 as esm2015
...
Angular 9 output with "target": "es5"
:
Compiling @angular/core : module as esm5
Compiling @angular/animations : module as esm5
Compiling @angular/compiler/testing : module as esm5
Compiling @angular/animations/browser : module as esm5
...
@jasonnutter Did we sort this?
No, we have not addressed this.
IE is not supported anymore, why do you need es5 now? As well as angular 9 which is not supported too
Closing as Ivy will be supported in msal-angular v3 (currently in beta) but will not be backported to v2. Please track issue #4298 for announcements on general availability of v3
Library
msal@1.x.x
or@azure/msal@1.x.x
@azure/msal-browser@2.x.x
@azure/msal-node@1.x.x
@azure/msal-react@1.x.x
@azure/msal-angular@0.x.x
@azure/msal-angular@1.x.x
@azure/msal-angular@2.x.x
@azure/msal-angularjs@1.x.x
Framework
Description
When using Ivy in Angular (> 9) and tsconfig.json targets ES5 the build fails with the following error. I can fix the error by switching to ES2015, but this is currently not an option because it breaks other functionality in the target app. Interestingly when I switch to ES2015, run a build and then switch back to ES5 it works despite building with --delete-output-path.
Error Message
MSAL Configuration
Build issue rather than configuration issue
Reproduction steps
tsconfig.json
Expected behavior
MSAL v2.0 builds for ES5 as well as ES2015, Ivy is supported.
Identity Provider
Browsers/Environment
Regression
Security
Source