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
Given I have in my package.json
"compy": {
"main": "Main.js",
"dependencies": {
"edjafarov/socker": "master"
}
} compy install and compy install -f won't update my compy entries, but compy install -f edjafarov/socker will update it and set version to '*'.
Is it as planned?
Can master branch be ahead of '*' ~latest release? Thus making dependency broken in case it has some sort of fix that wasn't part of release yet.
Maybe, compy should introduce some sort of update verb to safely get the latest component matching package version?
The text was updated successfully, but these errors were encountered:
Given I have in my package.json
"compy": {
"main": "Main.js",
"dependencies": {
"edjafarov/socker": "master"
}
}
compy install
andcompy install -f
won't update my compy entries, butcompy install -f edjafarov/socker
will update it and set version to'*'
.Is it as planned?
Can master branch be ahead of
'*'
~latest release? Thus making dependency broken in case it has some sort of fix that wasn't part of release yet.Maybe, compy should introduce some sort of
update
verb to safely get the latest component matching package version?The text was updated successfully, but these errors were encountered: