
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Boilerplate for static & microservices-based web applications.
It aims to provide some sort of Asset Pipeline for static and Node.js based projects.
$ npm install tribble --save-dev
Runtime configuration can be set through a .tribblerc file with the following keys :
Tribble is packaged with ESLint and Airbnb's ESLint base configuration, including ECMAScript 6+ rules. The source parameter can be used to override the default source parameter specified in the .tribblerc runtime configuration file.
$ ./node_modules/.bin/tribble lint [--source <folder>]
Tribble is packaged with Browsersync.
The serve command launch a browsersync server with the built-in static server pointing to folder on port number.
This command is intend to live preview web app's source file distribution and executed only preprocessor to aggregator plugins.
The source and port parameters can be used to override the corresponding parameters specified in the .tribblerc runtime configuration file.
$ ./node_modules/.bin/tribble serve [--source <folder>] [--port <number>]
The build command executed all installed plugins (from preprocessor to packager) on the source files distribution folder and processed/aggregated assets are copied to the production-ready files distribution target.
The source and target parameters can be used to override the corresponding parameters specified in the .tribblerc runtime configuration file.
$ ./node_modules/.bin/tribble build [--source <folder>] [--target <folder>]
Each plugin is designed to perform live processing (for the source files distribution through Browsersync middlewares) and/or build (for the production-ready files distribution).
Public plugins are provided for the most common processing tasks.
Current available public plugins are :
To install a public plugin :
$ ./node_modules/.bin/tribble install <plugin>
To uninstall a public plugin :
$ ./node_modules/.bin/tribble uninstall <plugin>
Public plugins are installed under the current project devDependencies flag.
You can also define private/local plugins like the public ones.
To do so, create a tribble.json file for one (or several) plugin(s) with the following structure (inspired by Swagger specification) :
{
"path/to/module1": {
"tags": ["preprocessor"], // plugin main caracteristics
"consumes": ["mediatype1", "mediatype2", ...],
"produces": ["mediatype1", ...]
},
"path/to/module2": {
...
}
}
Plugin characteristics (defined as tags) are used to order plugins and build tasks pipelines.
They can have the following values :
Each plugin module is defined as follow :
module.exports = (input, ouput) => {
const data = input.read();
... // any synchronous/asynchronous transformation to data object
ouput.send(data);
};
Please check the sass plugin for implementation example.
FAQs
Boilerplate for static & microservices-based web applications
We found that tribble 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.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.