Skip to content
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

@azure/msal-angular: peerDependencies operators don't imply support for Angular versions 6? #398

Closed
RobARichardson opened this issue Aug 16, 2018 · 8 comments
Assignees
Labels
enhancement Enhancement to an existing feature or behavior.

Comments

@RobARichardson
Copy link

RobARichardson commented Aug 16, 2018

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[x] Documentation issue or request
[ ] Other... Please describe:

Library version

@azure/msal-angular 0.1.1

Current behavior

Documentation for Msal-Angular says:

"...The MSAL library preview for Angular is a wrapper of the core MSAL.js library which enables Angular(4.3 and above)..."

However, peerDependencies imply the library only supports Angular v4.x:

"peerDependencies": {
"@angular/common": "^4.3.0",
"@angular/core": "^4.3.0"
}

This causes errors when using 'ng update' (Angular CLI) w/ Angular versions higher than 4:

Package "@azure/msal-angular" has an incompatible peer dependency to "@angular/core" (requires "^4.3.0" (extended), would install "6.1.3").
Package "@azure/msal-angular" has an incompatible peer dependency to "@angular/common" (requires "^4.3.0" (extended), would install "6.1.3").

Expected behavior

If msal-angular indeed supports Angular 5 & 6, no warnings should show up for @azure/msal-angular when using 'ng update' w/ those versions of Angular.

@nehaagrawal nehaagrawal self-assigned this Aug 16, 2018
@nehaagrawal
Copy link
Contributor

@RobARichardson There is no 'ng upgrade' command. I think you meant 'ng update'? Can you please tell me what was your local angular version when you ran the 'ng update'?

@RobARichardson
Copy link
Author

@nehaagrawal yes, I meant 'ng update'. I've edited my original post to correct the typo.

I'm using Angular 6.1.3

@nehaagrawal
Copy link
Contributor

nehaagrawal commented Aug 16, 2018

@RobARichardson I am going to release another version with a dependency/peer-dependency on angular 5.0. However you can use the current msal-angular version with angular 5.0. It works. Please check our dev samples. We are using angular 5 there. I am going to update the documentation that we currently support only 4.3.* to 5.

@RobARichardson
Copy link
Author

@nehaagrawal okay. Yeah, I noticed that the sample isn't up to Angular 6 yet. Any ideas on when support for 6 will happen and what is preventing it? We would really like to use msal-angular but can't downgrade to Angular 5.

@nehaagrawal
Copy link
Contributor

@RobARichardson On another thread I saw that you had some success by using rxjs-compat for rxjs breaking changes. Didn't that work?

@RobARichardson
Copy link
Author

@nehaagrawal yeah, using rxjs-compat worked great, but then I ran into the issues related to #386. Barring any other issues, I'll still try to use msal-angular in my Angular 6 project even though the library doesn't officially support it yet.

@nehaagrawal
Copy link
Contributor

@RobARichardson I have a fix for issue #386. I am ill releasing it in this week. You can still use msal-angular with angular 5. We don't have support for angular 6 yet but that's in our backlog and we will work on it in future.

@nehaagrawal nehaagrawal changed the title @azure/msal-angular: peerDependencies operators don't imply support for Angular versions 5 & 6? @azure/msal-angular: peerDependencies operators don't imply support for Angular versions 6? Aug 28, 2018
@nehaagrawal nehaagrawal added the enhancement Enhancement to an existing feature or behavior. label Aug 28, 2018
@nehaagrawal
Copy link
Contributor

closing this issue in favor of #421. Please track there for future updates.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Enhancement to an existing feature or behavior.
Projects
None yet
Development

No branches or pull requests

2 participants