Which is true since my tag styles are like: v0.0.1, v0.0.2 and so on…
If settings volo.url to https://raw.github.com/codefolding/eugene/v{version}/build/eugene.less instead, would probably make it work but break when trying to add the library using the master branch with volo add codefolding/eugene/master since it would result in vmaster?
The thing that makes me curious is that by using volo add codefolding/eugene/0.0.3 correctly points to the tag v0.0.3 however, that doesn't seem to be the same when volo.url is set.
The only way that I can make it work is by not creating a volo.url in package.json and when requesting the library, do so through volo add codefolding/eugene#build/eugene.less instead.
It would be quite nice if we could declare volo.url just as we do for dependencies (with support for github aliases) like:
I have the following package.json for my library:
However when trying to retrieve the latest version of the library, the result is:
Which is true since my tag styles are like:
v0.0.1
,v0.0.2
and so on… If settingsvolo.url
tohttps://raw.github.com/codefolding/eugene/v{version}/build/eugene.less
instead, would probably make it work but break when trying to add the library using themaster
branch withvolo add codefolding/eugene/master
since it would result invmaster
?The thing that makes me curious is that by using
volo add codefolding/eugene/0.0.3
correctly points to the tagv0.0.3
however, that doesn't seem to be the same whenvolo.url
is set.The only way that I can make it work is by not creating a
volo.url
inpackage.json
and when requesting the library, do so throughvolo add codefolding/eugene#build/eugene.less
instead.It would be quite nice if we could declare
volo.url
just as we do for dependencies (with support for github aliases) like: