Generate your static site with gulp plugins!
npm install --save-dev bulbo
First you need to set up bulbofile.js like the following.
const bulbo = require('bulbo')
const asset = bulbo.asset
// copy css
asset('source/**/*.css')
The above means that 'source/**/*.css' is asset and which will be copied to the destination directory (default: build).
If you want to change the destination you can do it with bulbo.dest method
bulbo.dest('output')
If you need to bundle your scripts with browserify you can set up it like the following:
const bundler = require('bundle-through')
// build js
asset('source/page/*.js')
.base('source')
.watch('source/**/*.js')
.pipe(bundler())
.base('source') means the base path of your glob pattern (source/page/*.js) is source..watch('source/**/*.js') means that this build process watches the files source/**/*.js, not only source/page/*.js.pipe(bundler()) registers bundler() as the transform. bundler() transforms all files into the bundles using browserify. See the document for details.To build html from layout tempate, set up it like the following:
const frontMatter = require('gulp-front-matter')
const wrap = require('gulp-wrap')
// html
asset('source/*.html')
.pipe(frontMatter())
.pipe(wrap(data => fs.readFileSync('source/layouts/' + data.file.frontMatter.layout).toString())))
.pipe(frontMatter()) means it extracts the frontmatter from the file..pipe(wrap(...)) means it renders its html using layour file under the source/layouts/.
layout property of the frontmatter.To exclude some patterns, use ! operator.
// others
asset('source/**/*', '!source/**/*.{js,css,html,lodash}')
The above copies all assets under source except .js, .css, .html or .lodash files.
The resulting bulbofile.js looks like the following:
const bulbo = require('bulbo')
const asset = bulbo.asset
const bundler = require('bundle-through')
const frontMatter = require('gulp-front-matter')
const wrap = require('gulp-wrap')
bulbo.dest('output')
// css
asset('source/**/*.css')
// js
asset('source/page/*.js')
.base('source')
.watch('source/**/*.js')
.pipe(bundler())
// html
asset('source/*.html')
.pipe(frontMatter())
.pipe(wrap(data => fs.readFileSync('source/layouts/' + data.file.frontMatter.layout).toString())))
// others
asset('source/**/*', '!source/**/*.{js,css,html,lodash}')
And then bulbo serve command starts the server.
$ bulbo serve
bulbo [01:33:38] Using: /Users/kt3k/tmp/long-dream-core/bulbofile.js
bulbo [01:33:39] serving
bulbo [01:33:39] Reading: site/**/*.js
bulbo [01:33:39] Reading: src/infrastructure/infrastructure.js
bulbo [01:33:39] Reading: site/*.html
bulbo [01:33:39] Reading: site/data/**/*.*
bulbo [01:33:39] Reading: site/img/**/*.*
bulbo [01:33:39] Reading: site/css/**/*.*
bulbo [01:33:39] Server started at: http://0.0.0.0:7100/
bulbo [01:33:39] See debug page is: http://0.0.0.0:7100/__bulbo__
bulbo [01:33:39] Ready: site/**/*.js
bulbo [01:33:39] Ready: src/infrastructure/infrastructure.js
bulbo [01:33:39] Ready: site/*.html
bulbo [01:33:39] Ready: site/img/**/*.*
bulbo [01:33:39] Ready: site/css/**/*.*
bulbo [01:33:39] Ready: site/data/**/*.*
And the following builds all the given assets and saves them to build/ directory.
$ bulbo build
bulbo [12:04:19] Using: /Users/kt3k/tmp/long-dream-core/bulbofile.js
bulbo [12:04:20] building
bulbo [12:04:25] done
const bulbo = require('bulbo')
This registers the glob pattern as the asset source.
Example:
bulbo.asset('src/js/**/*.js')
Example:
bulbo.asset('src/feature1/*.html', 'src/feature2/*.html')
This passes the option to asset globing.
Example:
bulbo.asset('src/js/**/*.js')
.assetOptions({read: false})
The above doesn't read actual file contents when being built. This is useful when you use the transform which doesn't require the file contents.
This sets the base path of the asset glob.
The base path is automatically chosen from your glob pattern. If you want change the default base path you can change it calling this method.
Example:
bulbo.asset('src/img/**/*.*') // `src/img/foo.png` is copied to `build/foo.png` because the base path of this glob is `src/img` by default.
bulbo.asset('src/img/**/*.*').base('src') // but in this case, copied to `build/img/foo.png`
This sets the watch path(s) of the asset. If no watch paths are set, the bulbo watches the same paths as the asset's source paths.
Example:
bulbo
.asset('src/js/pages/*.js')
.watch('src/js/**/*.js') // Watches all js files under `src/js`, though build entry poits are only js files under `src/js/pages`.
.pipe(through2.obj((file, enc, callback) => {
file.contents = browserify(file.path).bundle()
callback(null, file)
}))
This options is passed to chokidar's watch option. You can modify the behaviour of the internal chokidar as you want.
This sets the build destination. (The default is build)
Example:
bulbo.dest('dist')
This sets the port number of the asset server. (The default is 7100.)
Example:
bulbo.port(7500)
This sets the default base path for all the assets.
Example:
bulbo.base('source')
bulbo.asset('source/news/**/*.md')
bulbo.asset('source/events/**/*.md')
bulbo.dest('build')
The above assets build to build/news/**/*.md and build/events/**/*.md respectively.
npm install -g bulbo installs command bulbo. Which supports 2 subcommands build and serve.
This builds all the registered assets into the destination directory. The defualt destination is build. The path is configurable by bulbo.dest(path) in bulbofile.
This starts the local server which serves all the registered assets on it. The default port is 7100. The number is configurable by bulbo.port(number) in bulbofile.
bulbo command without arguments also does the same as bulbo serve. You can just simply call bulbo to start bulbo server.
The bulbo server has builtin debug url at 0.0.0.0:7100/__bulbo__. You can find there all the available paths (assets) on the server. It's useful for debugging the asset stream.
You can enable es2015 syntax by renaming bulbofile.js to bulbofile.babel.js and adding babel-register as dependency.
npm install --save-dev babel-register babel-preset-es2015
You also need to set up .babelrc as follows:
{
"presets": [
"es2015"
]
}
You need to rename bulbofile.js to bulbofile.coffee and install coffeescript dependency:
npm install --save-dev coffee-script
And your bulbofile.coffee looks like the following:
asset = require('bulbo').asset
through2 = require 'through2'
browserify = require 'browserify'
frontMatter = require 'gulp-front-matter'
wrap = require 'gulp-wrap'
asset 'source/**/*.css'
asset 'source/**/*'
asset '!source/**/*.{js,css,html,lodash}'
asset 'source/page/*.js'
.watch 'source/**/*.js'
.pipe through2.obj (file, enc, callback) ->
file.contents = browserify(file.path).bundle()
callback null, file
asset 'source/*.html'
.pipe frontMatter()
.pipe wrap (data) =>
fs.readFileSync("source/layouts/#{ data.file.frontMatter.layout }").toString()
Use gulp-if:
const gulpif = require('gulp-if')
const uglify = require('gulp-uglify')
const PRODUCTION_BUILD = process.NODE_ENV === 'production'
asset('source/**/*.js')
.pipe(gulpif(PRODUCTION_BUILD, uglify())
This uglifies the scripts only when the variable NODE_ENV is 'production'.
Or alternatively use through2:
const through2 = require('through2')
const uglify = require('gulp-uglify')
const PRODUCTION_BUILD = process.NODE_ENV === 'production'
asset('source/**/*.js')
.pipe(PRODUCTION_BUILD ? uglify() : through2.obj())
Use gulp-wrap and the engine option:
const wrap = require('gulp-wrap')
const frontMatter = require('gulp-front-matter')
asset('source/**/*.html')
.pipe(frontMatter())
.pipe(wrap({src: 'source/layout.nunjucks'}, null, {engine: 'nunjucks'}))
Note You need to npm install nunjucks in this case.
This example wraps your html in the nunjucks template. The contents of each html file is refereced by contents and the front matter by file.frontMatter.
Use watch option in the asset options.
asset('source/page/*.js')
.watch('source/**/*.js')
This is useful when the entrypoints of the asset and the actual source files are different. For example, if you use browserify to bunble your scripts, your entrypoints are bundle's entrypoint files but you need to watch all of your source files which form the bundles.
bulbo can be used as internal engine of your own static site generator.
The example looks like the following:
index.js:
const bulbo = require('bulbo')
bulbo.asset(...).pipe(...) // Some preset settings are here.
module.exports = bulbo
bin/index.js
const bulbo = require('bulbo')
bulbo.cli.liftoff('mycommand', {configIsOptional: true}).then(bulbo => {
bulbo.build()
})
and bin/index.js works as static site generator cli with some asset building preset.
$ node bin/index.js
This builds preset assets without your configuration. This is useful if you want to share the same bulbo setting across the projects.
This set up your module using liftoff. This returns a promise which is resolved by the your own module. Your module needs to implement setLogger method. It is recommended you expose bulbo module instance as your module interface.
This does not take care of cli options. It is recommended to use with option parsers like minimist, minimisted etc.
MIT
Bulbo = vinyl-fs + js-liftoff + stream-splicer + vinyl-serve + Bulbo DSL
vinyl-fs is the same as gulp.src() and gulp.dest(). Bulbo uses it for creating file streams and saving them.js-liftoff is a magical tool for creating CLI tool which is configurable by its DSL script, in this case like bulbofile.js.stream-splicer is used for creating a linear pipeline of transforms of the assets.vinyl-serve is a simple server which consumes readable vinyl streams and serves the files in them.Bulbo has the only one model Asset which represents a group of assets and its transform.
Bulbo has 3 application layer classes, AssetServer AssetBuilder and AssetService
Bulbo DSL is implemented in bulbo.js (the module interface) and AssetFacade class.
FAQs
Generate your static site with gulp plugins!
The npm package bulbo receives a total of 50 weekly downloads. As such, bulbo popularity was classified as not popular.
We found that bulbo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.