-
Notifications
You must be signed in to change notification settings - Fork 586
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
Allow ng2-select to work with ng4 #738
Comments
|
─ UNMET PEER DEPENDENCY @angular/[email protected] invalid |
I am afraid this may never be done, but that's a must if this library is to last a bit longer |
any news |
This lib is dead, let's move on. |
A forked version with relaxed dependencies can be used for now:
It can be installed on angular 4.x |
Ohh. It seems that the fork should also be rebuilt |
UPD:
|
Using npm version 5 solved the version locking issue. The new npm generates a package-lock.json file so no more npm shrinkwrap ! |
I still have sasme error even using ng2-select-compat. Any solution? |
@mouradhamoud I'm using npm 5 and still get the same problem. How does it work for you? |
@filipefreitas82 I have the line The generated package-lock.json contains:
I didn't need to do anything special. Extra details: I'm using npm v 5.3.0 and angular v 4.3.2, I hope this will help. |
@mouradhamoud thanks. As it turns out my problem was related to other packages (ngx-bootstrap and ngx-uploader). Still I'm using npm 5.3.0 with angular 4.3.6 and I'm getting the same warnings:
My package-lock.json also has the same as yours:
|
@filipefreitas82 Nice, I have the warnings too but this doesn't prevent the generation of the lock file. |
Is ng2-select 1.2.0 going to support angular 4 at some point? I'm getting the warning as stated here with node 8.1.2 and @angular/cli: 1.3.2 and angular 4.2.4. |
New life of the component in the fork: https://github.com/optimistex/ng2-select-ex |
When I try to npm install an ng4 project (4.0.0) that is using ng2-select, I get the following warning:
I believe that is because the peer dependencies of version 1.2.0 of ng2-select are locked to 2.x.x, see package.json:
It should also allow to be usable with ng4 without producing warnings during
npm install
.The text was updated successfully, but these errors were encountered: