v0

[IniZio]

For brainstorming and progress tracking.

Firstly, what is torbjorn for?

When i created clipped it was for grouping all kinds of config into one single object with jointed to make manipulations easier.

I thought unifying different ways of configuring libraries is easy but its actually pretty clumsy, since most libraries only provide some of the many ways like .xxxrc, package.json and command line arguments.

Instead of unifying, generators like yaoman might be a better solution.

But yaoman is a one-time boilerplate generator which is not really extendable, especially since you cannot revert a certain part of boilerplate.

I want to create torbjorn for a practical solution, unlike neutrino which has elegant code but hard to learn, or create-react-app that no one wants to read through its freaking codebase

So how will torbjorn solve it?

• Generator approach instead of plugin so that when users want to add features on top they can just refer to normal ways instead of learning jointed and clipped.config.js

• Make it so generators will have typings intellisense support, in clipped you had to refer to docs over and over again. Kind of like gulp maybe?

• You should be able to up() or down() parts of or the whole generator

• Generators themselves should be sustainable. The generator itself can provide fixed version, but there will be a hook before dev and watch that checks if there are any updates with https://www.npmjs.com/package/latest-version

  It should be give a cli prompt for confirmation before update instead of forcefully update

• TBD

Progress

• [ ] Instance
  • [x] utils: fs, git, prompts, config, resolve
  • [x] core: describe, run, dispatch
  • [ ] patch: before and after dispatch
  • [ ] init: git init, npm init
• [ ] CLI
  • Commands:
  • [x] run: Runs all actions
  • [x] dispatch <action1> <action2> ...: Dispatches named actions replaced with --only option in run
  • [ ] revert <action1> <action2> ...: Revert named actions
  • [ ] help
  • [x] version
  • Options:
  • [ ] --external: Fetches external turret (before any given command)
• [ ] Ecosystem
  • npm
  • git
  • editorconfig
  • js: bundler -> framework
• [ ] Rethink
  • config loader: config.require() instead of config('torbjorn')?
  • ast:

[IniZio]

One way to make up/down() easy is using git patch, but will require the project to be using git

[IniZio]

Prototyping config at https://gist.github.com/IniZio/45282dbdba2ddc144f8fbbaa59141f8d

[IniZio]

Config transform tools:

• json5
• https://www.npmjs.com/package/config.ini
• https://github.com/mohsen1/yawn-yaml
• https://github.com/nodeca/js-yaml

Nice reference:

• https://github.com/kaelzhang/rc-parser
• https://github.com/davidtheclark/cosmiconfig/