Jade plugin for component-builder
Jade plugin for component-builder2.
var fs = ;var build = ;var jade = ;buildscriptsnodes
You could put your jade files in
.templates or create your own field like
Without the global runtime, you have to define the
visionmedia/jade dependency in every component that uses jade templates. This is quite annoying:
If you want to avoid this as, use the global runtime.
string- compile the template as an HTML string instead of a function.
runtime- use the global runtime instead of using a local
jadedependency. See below.
You may use the global runtime by prepending
jade.runtime to your build and using the
This will create a global
jade variable. However, the benefits are:
visionmedia/jadeas a dependency in every component
However, you now essentially have to manage this dependency yourself.
The MIT License (MIT)
Copyright (c) 2014 Jonathan Ong email@example.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.