You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use bower for package management, and I want the bower_components directory under public. Upon harp compile, I want the entire bower_components directory to be copied over to wwwbut not be compiled/parsed. For example, Twitter Bootstrap's bower component includes a bunch of .less files, and upon harp compile, harp attempts to compile those files.
Some ideas on usage:
Allow for a special flag in _data.json or _harp.json to tell harp compile (and harp server, while we're at it) to avoid compiling a set of files. Maybe something like this
Allow harp compile to accept a list of files/directories that will only be copied to destination, not parsed/compiled. Maybe something like harp compile --copy-only="public/bower_components" or something.
The text was updated successfully, but these errors were encountered:
Yeah I am on board with this outcome, but I think it should just read the .gitignore file or something like that. I’m having the same problem with node_modules/, I can’t use some modules because Harp chokes on compiling them. It also slows everything down a lot when 90% of you app’s filesize is in a components directory, but you don’t actually need the output.
I keep /node_modules outside of the harp public/ folder.
I think using .gitignore is a good step in the right direction, but I do commit bower components to the repo on lots of harp sites, though not on all sites. I'd like to be able to commit to the repo and separately instruct harp on whether to compile a given folder or path or glob. Thoughts?
If you have an example repo where you’ve committed the Bower components, that would probably be helpful for us. Eventually we’d like to support node_modules properly, so it could be outside public/ but still be available as you’d expect. I’d like to factor Bower and Component in when we do that, but it probably won’t happen right away.
Use case example:
I want to use bower for package management, and I want the
bower_components
directory underpublic
. Uponharp compile
, I want the entirebower_components
directory to be copied over towww
but not be compiled/parsed. For example, Twitter Bootstrap's bower component includes a bunch of.less
files, and uponharp compile
, harp attempts to compile those files.Some ideas on usage:
_data.json
or_harp.json
to tellharp compile
(andharp server
, while we're at it) to avoid compiling a set of files. Maybe something like thisharp compile
to accept a list of files/directories that will only be copied to destination, not parsed/compiled. Maybe something likeharp compile --copy-only="public/bower_components"
or something.The text was updated successfully, but these errors were encountered: