Node.js workflow tool
support unknown options for factory's commands
fbi built-in commands do not support unknown options
Example:
# Original command:
fbi build --mode <mode>
# Support execution:
fbi build --mode production --unknown uuu op
# Parsed result:
{ args: { mode: "production" }, unknown: ["--unknown", "uuu", "op"]}
New docs site: https://fbi-js.github.io/docs/pages/4x/
A factory is a collection of templates and commands in a similar application environment.
For example:
We also supply the factory-factory for factory development, and factory-commands for global commands.
We recommend using fbi link
and fbi unlink
for local factory debugging.
Scaffolding a project like Yeoman, with custom features and logic.
Sub Template is a very useful new feature for scaffolding. e.g.: Extraction a vue component creation as a sub template of the vue
template in factory-web
, it is only available when the current project created via the vue
template.
Factory version(formerly template version
) has been improved through the separation of directories, so you can use different versions of a factory at the same time now. e.g: factory-web
, factory-web__1.0
, factory-web__2.0
, factory-web__2.1
.
Factories and project info are stored in fbi global store (~/.fbi
). They won't change when install or uninstall fbi or change nodejs version.
clean
: clean info in storeinfo
: show context infolink [factories...]
: link local factories to the storeunlink [factories...]
: unlink factories from the storetemplate
: install dependencies automatically after template updated (fbi up [template name]
)
fix ExperimentalWarning: The fs.promises API is experimental
package.json
when initializing a project.module.exports
or not.Here is the documentation for fbi 3.
Here is a new templates collection.
Here is a migration task if you want to migrate from fbi 2 to fbi 3.
fbi <command>|<task> -D
use
, set
, reset
commands.cat
, backup
, recover
commands.clone
with add
.pull
with update
.add-tmpl
add-task
with add
.rm-tmpl
rm-task
with remove
.Now fbi requires the task file directly instead of run it in vm. Avoid these problems. You can still get the current process context with ctx
.