fliphub/flipchain

NOTICE: replaced by https://github.com/fluents/chain-able

🏗💠 fliphub

the builder, of builders.

👾 all you need

see the example

enables configs that would take hundreds or thousands of lines, with just a few properties.

const FlipHub = require('fliphub')
new FlipHub({entry: './src/index.js'}).build()

📦 installation

yarn add fliphub
npm i fliphub --save

🗝️ legend

• introduction
• all the apps
• flipfam
• fliphub-core
  • presets
  • hubs
• examples
• apps
• cli
• terminology

📅❗ changelog

keep up to date! updated frequently.

all the apps

one app? two apps? 100 apps? fusebox, rollup, and webpack? nodejs server, inferno, and react? existing configs? happy and no happy pack? at the same time? no sweat.

const FlipHub = require('fliphub')

// take an existing config, flip it to fusebox or rollup or webpack
const config = require('./webpack.config.js')
config.flips = {to: 'fusebox'}

const apps = [
  config,

  {
    name: 'infernod',
    entry: './src/index.js',
    presets: ['inferno', 'neutrino-preset-happypack', 'web'],
  },
  {
    name: 'backend',
    entry: './backend/src',
    presets: ['node'],
  },
]

FlipHub.init({apps}).build()

♻️ reusability?

const { FlipHub } = require('fliphub')
const apps = [
  {
    name: 'reacted',
    presets: ['react'],
  },
  {
    name: 'infernod',
    presets: ['inferno'],
  },
]

FlipHub.init({
  presets: {
    reusable: {
      entry: './src/index.js',
      flips: {to: 'fusebox'},
    },
  },
  apps,
}).build()

they are configured for each environment by default and can be customized for any config you want

⚠️ the problem

• build systems are notorious for their difficulty.
• finding and setting up the right
  • scripts
  • plugins
  • loaders
  • configs
  • requiring the dependencies
  • bloating your config files
  • making configs for
    • development bundling
    • production bundling
    • production dev bundling
    • test environments
    • development servers
    • production servers
• tedious, with a high barrier of entry
• time intensive; switching build systems for 1 app is grueling
• ... all of the above for every application

✔️ the solution

• with the flip of a flag, you can go from webpack, to fusebox, to rollup or any other supported build system.
• existing configs can be used and enhanced with ease.
• easily create presets & hubs to start converting your build system to another, flip the switch to keep compatibility without breaking everything,

📘 examples

• examples-minimal
• examples-canadas
• examples-monorepo
• examples-react
• examples-react-and-alias
• examples-typescript
• examples-node
• examples-lint
• examples-compat 🚧
• examples-tests 🚧
• examples-webworker 🚧
• examples-code-splitting 🚧
• examples-es6-ts-config 🚧
• examples-flags 🚧

📚 documentation

• 📖 see the wiki
• 🚧 see the work-in-progress docs

💠 hubs (middleware +)

docs hubs

🚩 flags

☕🏳️ filters

white-list flags are used to filter which apps are run for different operations

🏹 aliasing

see the alias docs

🍰 presets

see the preset documentation

const apps = [{
  presets: ['alias-resolve', 'neutrino-preset-web', 'eslint'],
}]

const appsWithArgs = [{
  presets: {
    aliasResolve: __dirname,
    presetWeb: null,
    eslint: require('./.eslintrc.js')
  },
}]

v0

v0 is still available as flipbox but is unmaintained.

flipchain's Issues

upgrade .clear

with .clear, it clears properties that are chains, but if those chains happen to be other chains that include this particular chain, it will infinitely .clear

needs thought for best way to handle (could use temp property for .clearing), or pass in property true to force .clear recursively

add `browser`/`web` module field excluding inspector