Helper

Determine the boot order of plugins based on their bajo.bootorder property in their package.json file. If not provided, the plugin will be booted in the order they are listed in the package.json file or .plugins file.

Building Bajo configuration object. Called after all config handlers are collected, this function will read config files written in any of config handlers' supported formats:

• if runtime configuration object is provided (the one passed to the app constructor), it will be used as the base. Otherwise, files are read from the {dataDir}/config
• then it will be merged with the configuration coming from the command line arguments and environment variables
• doing some normalization and validation works, including setting the language, environment, log level, and cache purge settings
• and setting up the app's log instance with the proper log level

Load, build and sanitize all plugins defined in package.json or .plugins file, and add them to the app's plugin list. It will also make sure the main plugin is there too, if not, it will be created with the default template and settings.

Finally, it will loop through all loaded plugins and its config and language files.

This function is called by Bajo during the initialization process.

Ensure all plugins' dependencies are met. If there is a missing dependency, an error will be thrown.

Semver is also supported, so if a plugin requires a specific version of another plugin, it will be checked as well.

Ensure the uniqueness of all plugins' name and alias. If there is a clash, an error will be thrown.

Collect all plugins' config handlers and push them to the app's configHandlers array.

Collect all plugins' hooks and push them to the app's hooks array.

Collect all plugins defined in package.json or .plugins file, and add them to the app's plugin list. It will also make sure the main plugin is there too, if not, it will be created with the default template and settings.

Ensure the existence of necessary directories for Bajo. This function is called by Bajo during the initialization process:

• it sets up the base directory,
• it checks the validity of the data directory,
• it ensures the temporary directory exists,

Attach plugins exit handlers to make sure when the app shuts down, all plugins shut down gracefully first

Find item deep in paths.

Freeze object.

Import file/module from any loaded plugins.

E.g. your plugin structure looks like this: |- src | |- lib | | |- my-module.js |- index.js |- package.json

And this is how to import my-module.js: javascript const { importModule } = this.app.bajo const myModule = await importModule('myPlugin:/src/lib/my-module.js')

Outmacth with support for scoped source and pattern. Scoped source/pattern is a source/pattern that has a plugin's namespace prefix, separated by : symbol.

This function is usefull for matching a source/pattern that is scoped to a specific plugin's namespace. For example, if you have a source myPlugin:foo/bar and a pattern myPlugin:foo/*, this function will return true because the source matches the pattern within the same namespace.

Parse object and normalize their values.

Support automatic value translation for keys with t: prefix. The keys are then converted to the one without the t: prefix, and the original key is removed from the object.

See aneka.parseObject() for more details.

If app is in applet mode, this little helper should take care plugin's applet boot process

Run all loaded plugins' init() and start() methods in the order determined previously during boot process.

Normalize file path to lock file. If the provided file is an absolute path, it will be returned as is. Otherwise, it will be converted to a lock file path in the temporary directory of the application.

Acquire a lock on a specified file to prevent concurrent access.

Shortcut to aneka.setInterval() with Bajo's lockFile support.

Unlock a specified file that was previously locked, allowing concurrent access again.

If file does not exist, it will return true immediately.