- I accidentally put it into build-default before build-options existed,
  but the test very specifically tests an option, `--target node`, so
  it should be in build-options as that's not a zero-config default

- the previous console.log statement would actually log out because
  one of the tests imports (`require`s) the actual built library in
  order to ensure correctness
  - during the import, the side-effect runs and prints, which ends up
    actually printing out during the test, which was quite noisy 😅

- we do still want a side-effect so the whole statement doesn't get
  removed as dead code, so use a global variable assignment instead

- instead of random names (which are bad practice), be very explicit
  about what the variables _should_ be
- also add comments to some of the regression tests that didn't have
  any to describe them

- similarly, when testing dev only logging, say that directly
  - and, in this case, instead of using an unnecessary swear word
    - the third contributor PR to TSDX removed some similar swear words
      in the templates
      - these were changed to "boop" and now similarly changed to be
        more descriptive
        - which is better practice anyway, not encouraging bad practices
          via the templates, and should also be easier to understand for
          newcomers

- similarly, intead of "blah" and "works" in template tests, actually
  describe what the tests do
  - similarly encourage better practices in the tests

- also rename template tests from "blah.test.ts" to "index.test.ts"
  because they test "index.ts" and it's common convention to name them
  the same

- and fix a leftover "describe('it')" in the react template when it
  should be "describe('Thing')" which the storybook template has
  - "it" is also confusing when used together with the Jest "it" global
  - could use something better than "Thing" as well (e.g.
    "SomeComponent"), but don't want to dig through and re-test the
    Storybook pieces right now

- it uses normal .ts files and no JSX (that's what the React template
  is for after all), so README shouldn't mention .tsx

- woops, this was probably a copy+paste error on my behalf when I was
  improving the basic template's docs

- have most of the syntax tests export a function that returns true
  if the syntax is evaluated correctly, and test that it does in fact
  return true
  - just using `true` as something consistent and easy to test for

- change the async test to move the side effect before the Promise
  resolves
  - not entirely sure why, potentially because of the way the event
    loop works (race condition), but this was returning false when
    after and true when before
    - both work as a side effect, so just have it before

- several of the dependencies in the tree are only there because they
  are peerDeps, and not because we directly depend on them
  - they should only be upgraded in tandem with the dep(s) they are
    peers of and pretty much never in isolation

- Greenkeeper made several PRs for peers which previously caused an
  erroneous/buggy update of `@types/jest` to 25 many months before Jest
  was upgraded to 25
  - and honestly those Greenkeeper PRs for peers had confused me a
    good deal too

- relative links in website were not working as the files can't be viewed
  on the site
  - these were erroneously copy+pasted from the README, where the relative
    links work by pointing to files in the repo
    - those relative links don't work on the website

- use absolute links instead to the main fork of the repo's `master` branch
  - this has a few caveats now, in that the README has a bit more desync from
    the website now and that, unlike the README, these point to a specific
    fork and branch
    - the README points to the same version; regardless if forked or on a
      different branch, it'll point to that branch's code

* docs: update README.md [skip ci]

* docs: update .all-contributorsrc [skip ci]

Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>

Co-authored-by: Jared Palmer <jared@palmer.net>

Co-authored-by: Jared Palmer <jared@palmer.net>