|- 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
-
-
Save brianleroux/6954799 to your computer and use it in GitHub Desktop.
I think a manifest file would be a slightly better way to handle this as well. It's very similar in more established static site generators and is very common place in the Ruby world. Middleman has a nice implementation of this, it just uses Sprockets on the backend (https://github.com/sstephenson/sprockets)
While a "smart directory" would be very nice and may work for the majority of use cases, I've often found myself having to load my javascript files in a specific order.
All of that said, there are certainly utilities like GruntJS that can handle more specific needs so I'm sure everyone will use the tools that best suit them. Either way a step in this direction would be a nice addition.
Just my 0.02.
I think straight browserify combined with the leading _
convention would be ideal, since it follows the existing convention of using preprocessor-specific include mechanisms (Jade mixins, LESS) and is super simple to understand — just require("./_includes/my-include.js")
. Appeal to orthogonality. Also bonus that it supports NPM packages.
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 :)
@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
@sintaxi, here's a simple example if the files are just concatenated in lexicographical order:
main.js/foo.coffee
main.js/utils.coffee
Output from Harp: main.js
Because
f
comes beforeu
the order of the files is wrong and we get an error. Browserify or other module-related stuff can help, but I'd be wary of pushing browserify on everyone. You could also name your files starting with a number, for example, but then you lose lexicographical order in your text editor/file manager. An alternative implementation that's fairly straightforward would be to support pre-processing the file looking for special comments, e.g. something like this:main.coffee
The special comment would be replaced with the contents of
_utils.coffee
and then the entire file can be compiled to javascript. Note: I changed the name ofutils.coffee
to_utils.coffee
in this case since we don't want autils.js
in the final output.I'm not saying the special comment is the best approach, just trying to provide an alternative that could work. I'd love to hear your thoughts on all this.