Make and use updatable project templates. Regenerate code without losing custom changes. Framework agnostic.

• Why
• What
• How
• Help
• Usage
• Commands

After you generate code with a template or tool, you make changes. But then usually you can't regenerate the code without losing your changes. So you can't apply an updated template or change to another one supporting the same inputs. Keeping your "legacy code" current becomes an expensive pain.

ns-flip is a CLI to support creating and using project generators that can be exchanged as easily as WordPress themes. Here is a sample with 1 minute video.

A "template" can generate any combination of three types of files:

1. standard (appear in every generated code base, e.g. App.jsx)
2. custom static (static, but must be custom specified for each code base, e.g. steps in an input stepper)
3. custom dynamic (based on queries e.g. components showing query results).

You can create templates with locations designated for custom code within the generated files. You can also name regions that can be replaced or removed in the generated code. Ns-flip stores the custom changes before regenerating and then restores them.

See some standard use cases.

A template is a directory with requirements explained in the documentation. You can use it privately or distribute it.
You will need a basic working knowledge of Handlebars and not much more.

1. Build a template from sample code by calling ns newtemplate with a sample code base.
2. Generate or regenerate code from the template : ns generate $CODE [-t $TEMPLATE. All safe changes to $CODE are preserved. There's a settings file for the code base that determines what is generated.
3. Modify your requirements by running ns settings $CODE. Just answer the prompts.
4. Add custom code. But periodically run ns check $CODE to be sure you are doing it safely. (Otherwise, some of your changes will not be preserved when ns generate is run in the future.)

• Read our documentation
• Post questions on our Community
• open issues

$ npm install -g ns-flip
$ ns COMMAND
running command...
$ ns (-v|--version|version)
ns-flip/2.5.0 linux-x64 node-v14.9.0
$ ns --help [COMMAND]
USAGE
  $ ns COMMAND
...

• ns check CODEDIR
• ns contact [MESSAGE]
• ns filediffs TEMPLATEDIR
• ns generate CODEDIR
• ns help [COMMAND]
• ns newtemplate
• ns settings CODEDIR

Confirms that your custom changes have been entered safely, allowing you to generate with an updated or replaced template, or with a changed 'ns.yml' file. Essentially, generates a new version of the code and then simply compares it against your current version. If there are differences, then there is a problem with your code. For documentation about safe custom code changes, please see https://ns-flip.nostack.net//Safe-Custom-Code.

USAGE
  $ ns check CODEDIR

ARGUMENTS
  CODEDIR  directory containing the code to check

OPTIONS
  -h, --help  show CLI help

EXAMPLE
  $ ns check ~/projects/myapp

See code: lib/commands/check.js

send feedback or request to ns-flip. Optionally provide email and other fields.

USAGE
  $ ns contact [MESSAGE]

ARGUMENTS
  MESSAGE  the message to send

OPTIONS
  -e, --email=email  email of sender
  -h, --help         show CLI help

EXAMPLES
  $ ns contact "how do I set up comment delimiters with escape chars?" -e [email protected]
  $ ns contact "generate is breaking when I add handlers."

See code: lib/commands/contact.js

compare the files in your sample target code and in the code being generated. In some cases makes suggestions.

USAGE
  $ ns filediffs TEMPLATEDIR

ARGUMENTS
  TEMPLATEDIR  directory containing the template

OPTIONS
  -c, --codeDir=codeDir    code directory.  Will override the default
  -h, --help               show CLI help
  -s, --modelDir=modelDir  model directory.  Will override the default

EXAMPLES
  $ ns filediffs $TEMPLATE
  $ ns filediffs $TEMPLATE -c $CODE -m $MODEL

See code: lib/commands/filediffs.js

generates code based on a template and an 'ns file'. To set the template, you need the template flag.

USAGE
  $ ns generate CODEDIR

ARGUMENTS
  CODEDIR  directory containing the code to check

OPTIONS
  -h, --help                     show CLI help

  -n, --noSetup                  Do not update the startup routine (this is only relevant when the templateDir flag is
                                 also used). Saves a lot of time for a template developer.

  -t, --templateDir=templateDir  Template directory. Will generate from the template, and will override any prior
                                 template or template version used.

EXAMPLES
  $ ns generate ~/ns/samples/out -t ~/ns/templates/basicTemplate
  $ ns generate $CODE -t $TEMPLATE --noSetup
  $ ns generate $CODE

See code: lib/commands/generate.js

display help for ns

USAGE
  $ ns help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

create new template.

USAGE
  $ ns newtemplate

OPTIONS
  -h, --help                     show CLI help
  -m, --model=model              directory containing the model code base from which you want to template
  -t, --templateDir=templateDir  directory for the template

EXAMPLE
  $ ns newtemplate -m $MODEL -t $TEMPLATE

See code: lib/commands/newtemplate.js

create new template.

USAGE
  $ ns settings CODEDIR

ARGUMENTS
  CODEDIR  directory containing the code

OPTIONS
  -h, --help  show CLI help

EXAMPLE
  $ ns settings $CODE

See code: lib/commands/settings.js