search

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

Support placing source files in a src directory instead of top level #179

Closed ewinslow closed 10 years ago

ewinslow commented 10 years ago

I just can't bring myself to put source files at the top level of the repo. Not all files at the top level are sources. This leads us to managing an excludes list (the current solution), which will probably always be incomplete and needing local customizations, or specifically enumerating the source files, which is equally tedious.

I would much rather put files in a src dir and then tell volo what the intended namespace of that directory is. No ignores be necessary.

jrburke commented 10 years ago

You could decide to use the github releases capability to create a zip file of just that src directory, and the use the volo.url to point to the releases zip file. Otherwise, ingore lists are fairly common for package managers.

Closing as I believe this is just a discussion ticket right now. Feel free to continue discussion here, and we can reopen as needed.