You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v1.6.2 is not backwards compatible with v1.6.1 projects #182
When we bump up the version of loopback-datasource-juggler required by loopback to a different major/minor version, we must release this change as a minor version of loopback.
We should also change the loopback version required by loopback-workspace and publish a patch version. I have updated the list of actions in the issue description.
Maybe we should collaboratively release a list of loopback related modules as we now have dual licenses for most of them. It will set a new baseline.
That's fine too.
Whatever way we choose, we should unpublish loopback@1.6.2 as soon as possible. It has already affected @mschmulen (strong-cli#107) and CI builds of loopback-angular (loopback-angular#19).
For me, the src of my problem was an out of data sls-sample-app that had been npm linked (for no good reason, I think I linked every strongnode module a month ago).
By doing an npm update in my sample app, the peer conflicts went away. Then I unlinked the sls-sample-app, because it didn't need to be linked.
Activity
bajtos commentedon Feb 18, 2014
We should also change the loopback version required by loopback-workspace and publish a patch version. I have updated the list of actions in the issue description.
raymondfeng commentedon Feb 18, 2014
Maybe we should collaboratively release a list of loopback related modules as we now have dual licenses for most of them. It will set a new baseline.
Upgrade devDependencies
bajtos commentedon Feb 18, 2014
That's fine too.
Whatever way we choose, we should unpublish loopback@1.6.2 as soon as possible. It has already affected @mschmulen (strong-cli#107) and CI builds of loopback-angular (loopback-angular#19).
bajtos commentedon Feb 23, 2014
@sam-github run into this problem too.
sam-github commentedon Feb 23, 2014
For me, the src of my problem was an out of data sls-sample-app that had been npm linked (for no good reason, I think I linked every strongnode module a month ago).
By doing an npm update in my sample app, the peer conflicts went away. Then I unlinked the sls-sample-app, because it didn't need to be linked.
bajtos commentedon Oct 15, 2014
Nobody should be using v1.6 by now, I am closing the issue as no longer relevant.