Adding # css file ends up with duplicate .css extensions

volojs / volo

Create front end projects from templates, add dependencies, and automate the resulting projects

https://volojs.github.io/

Other

1.41k stars 100 forks source link

Adding # css file ends up with duplicate .css extensions #159

Closed gregglind closed 11 years ago

gregglind commented 11 years ago

My desired outcome:

replace all my various Makefile curl calls with volo :) (is this reasonable?)

My blocker:

some assets are css files I want
some are directories
some are single (built) js files.
some are packages. (VOLO IS AWEOME)

In particular,

given this tree:

.
- css
- js

I can't figure out how to get this to do the "Right thing"

volo install twitter/bootstrap#docs/assets/css/bootstrap.css   css/boostrap.css

In particular, there is a lot of magic (that seems hard to diagnose -vv option wanted) about the from and where of files :)

gregglind commented 11 years ago

More specifics:

  "volo": {
    "dependencies": {
      "lib/user-actions": "github:gregglind/heatmap/dev#lib",
      "data/user-actions": "github:gregglind/heatmap/dev#data"
    }
  }

I expect this to literally put the contents of #lib and #data at those (uncreated) folders.
I have no idea of how to 're-call' this. If I do install -f it rewrite the package.json

Clearly I am not grokking the idioms and magic here :)

jrburke commented 11 years ago

I just tried this, and I notice in this particular case is the package.json: https://github.com/gregglind/heatmap/blob/dev/package.json

it lists some dependencies, which may the source of the confusion -- the package.json dependencies are installed even when #dev sub-parts are installed. Does that explain what was not expected?

For the bootstrap example, it looks like it works, but names the file boostrap.css.css. So that extra .css is definitely a bug and will fix that for the next release.