Table of Contents

Installation

This module is distributed via npm which is bundled with node and
should be installed as one of your project's devDependencies:

npm install --save-dev orther-scripts

Usage

This is a CLI and exposes a bin called orther-scripts. I don't really plan on
documenting or testing it super duper well because it's really specific to my
needs. You'll find all available scripts in src/scripts.

This project actually dogfoods itself. If you look in the package.json, you'll
find scripts with node src {scriptName}. This serves as an example of some
of the things you can do with orther-scripts.

Overriding Config

Unlike react-scripts, orther-scripts allows you to specify your own
configuration for things and have that plug directly into the way things work
with orther-scripts. There are various ways that it works, but basically if you
want to have your own config for something, just add the configuration and
orther-scripts will use that instead of it's own internal config. In addition,
orther-scripts exposes its configuration so you can use it and override only
the parts of the config you need to.

This can be a very helpful way to make editor integration work for tools like
ESLint which require project-based ESLint configuration to be present to work.

So, if we were to do this for ESLint, you could create an .eslintrc with the
contents of:

Note: orther-scripts intentionally does not merge things for you when you start
configuring things to make it less magical and more straightforward. Extending
can take place on your terms. I think this is actually a great way to do this.

Inspiration

This is inspired by react-scripts.

Other Solutions

I'm not aware of any, if you are please make a pull request and add it
here! Again, this is a very specific-to-me solution.