-
Notifications
You must be signed in to change notification settings - Fork 430
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
relax peer dependency to support angular 4.0.0 #636
Comments
On 1.3.1 i get the following errors
Packages
|
Seeing the same as @Drol, look like maybe ngm is picking up & merging the peer dependencies in src/package.json in the build step? |
I'm also having the same problem as @Drol
|
Same here. Is there a current work around to getting rid of these warnings? |
+1, please get rid of fixed versions as well: "@angular/compiler": ">=2.0.0 || >=4.0.0-beta.0" |
+1 |
2 similar comments
+1 |
+1 |
@vaidd4 I'm pretty sure it's because the build tool being used, ngm-cli, is merging this package.json from the src folder, and using the versions it finds in the root package.json's devDependencies. So I figure either the peerDependencies versions of compiler & forms need to be explicitly set in the root package.json, like core & common, or they need to be removed from the src/package.json. I haven't made a PR because I'm not sure which is more appropriate |
+1 |
1 similar comment
+1 |
+1 |
1 similar comment
+1 |
Committed fix regarding @angular/compiler & @angular/forms fixed version and migrated Karma to @Angular/CLI approach in order to fix failing test run based on this |
Chill out, this fix is literally just two lines of warnings no longer appearing when you do a build. Will be the only thing in 1.3.2 when that's released, I'm not in charge of that though. Shouldn't have closed in the commit message, I meant to just close the PRs. |
Actually this causes more than just a warning if you work with NPM Shrinkwrap. When you try to create a shrinkwrap, it will fail with the following errors.
|
Folks at valor-software are in charge of releasing. I asked about a week ago, got a reply but no action yet. |
Somebody needs to fork this, it meets all the criteria of dead software. When you can't even get a 3 character change done in 2 months... |
If valor is not actively maintaining this I too am all for forking. It is a great library and it would be a pity if it stalls. There are not many good dnd libs for Angular4 out there. What would be in improvement on react-dnd would be to enable proper touch enabled drag/drop/sort (AFAIK dragula does that to some degree). |
It is fixed on master branch. How can I include it in npm directly from github? |
psss... A new release is comming soon ;) |
Since the version 1.5.0 is out we can close this issue?! @Ketec |
published |
Where is 1.5.0? It's not in the list of releases: https://github.com/valor-software/ng2-dragula/releases |
currently it results in "requires a peer of" warnings.
It works on current angular 4 release, so perhaps the peerDep could be relaxed to >=4.0.0?
The text was updated successfully, but these errors were encountered: