|- node_modules/
|- src/
| |
| |- index.js/ <----------- uses browserify so anything in node_modules is game for require()
| | |- index.js
| | '- foo.coffee
| |
| |- index.css/ <---------- uses topcoatify so anything in node_modules is game. how import/etc works needs consideration
| | |- index.css
| | '- bar.styl
| |
| |- index.md
| '- _layout.ejs
|
|- www/ <--------------------- everything in here is generated from above
| |- index.js
| |- index.html
| '- index.css
|
|- package.json
'- readme.md
Created
October 12, 2013 20:53
-
-
Save brianleroux/6954799 to your computer and use it in GitHub Desktop.
fantasizing about some future integrations. - bringing harp some awareness of smart directories to build concat/min into convention
- browserify for harp would be sweet
- topcoatify does not yet exist but increasingly we something like it should exist
- next www can just 'disappear' as that it becomes a build artifact
@sintaxi, any updates on this feature? This is by far my biggest issue with Harp at the moment. If I have to write a separate build system for concatenating my scripts then I might as well not use Harp 😦
@sintaxi ... Any updates on this?
Having the ability to concatinate JS, set bower_components
to copy only and ignore node_modules
would allow me to win any conceivable argument for using Harp instead of Grunt or Gulp.
+1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Oops, realized Browserify requires included modules follow the Node.js module convention of assigning a public interface to module.exports, so wouldn't work with arbitrary JS. I'm a node-ecosystem n00b :)