SuperDRY

Modern problems require modern solutions, yet modern bundlers have not risen up to the challenge. With the venture funded, media hyped rise of boot camp graduates flooding our industry, Clean Coding standards are gradually being eroded by the filthy paws of amateur hour keyboard monkeys. These impostors bang away at their laptops but entropy increases with each tap. They cannot even print Hello World without importing a billion node_modules. They don't even know vim. Their odds of writing good, fast code are no higher than their combined hopes of producing the collected works of Shakespeare. This has to stop.

Many (more lenient) tech leads have resorted to using linting tools to keep this code clean and DRY. This approach is far too timid by half - linting tools can be easily bypassed by tweaking build scripts and so the guarantee of DRYness is weak. It is better to take a compiler/bundler approach to guarantee DRY code so that WET code doesn't even run.

Superdry projects don't merely practice Best Practices, they live it.

Best Practices

Here are some of the battle tested best practices everybody should adopt.

Single Responsibility Principles

Zero Dependencies

Quick Start

npx superdry init sourceFolder

That's it. You don't need to worry about setting up Typescript or Rollup or Jest or other plumbing. Just start editing init and go!

Below is a list of commands you will probably find useful:

superdry init

TODO: TEXT HERE

superdry build

TODO: TEXT HERE

superdry decompose

TODO: TEXT HERE