Total Overhaul (but with all the same fixtures!) (Kong#248)

see Kong#248 and the commits therein for more context.  Essentially:
- the original client fixtures were unchanged, which hopefully means the 
- all source code is now in strict mode TypeScript
- tests are now all in jest
- the file structure was reorganized so that everything for a particular client is in one place
- the CLI is updated and now using yargs
- all dependencies were updated and some (i.e. `format.utils`) were able to be removed entirely
- more work left to do (including CI with GitHub Actions, for example), but this is a start

Author: dimitropoulos

.editorconfig

@@ -9,5 +9,15 @@ charset = utf-8
 trim_trailing_whitespace = true
 insert_final_newline = true
 
+[targets/**/fixtures/*]
+insert_final_newline = false
+
+[**/http1.1/fixtures/*]
+end_of_line = crlf
+insert_final_newline = false
+
+[**/http1.1/fixtures/jsonObj-multiline]
+end_of_line = unset
+
 [*.md]
 trim_trailing_whitespace = false

.eslintignore

@@ -0,0 +1,3 @@
+src/targets/**/fixtures
+dist
+bin

.eslintrc.js

@@ -0,0 +1,30 @@
+/** @type { import('eslint').Linter.Config } */
+module.exports = {
+  parser: '@typescript-eslint/parser',
+  env: {
+    node: true,
+  },
+  parserOptions: {
+    project: 'tsconfig.json',
+  },
+  extends: [
+    'eslint:recommended',
+    'plugin:@typescript-eslint/recommended',
+    'plugin:jest/all',
+    'plugin:jest-formatting/strict',
+    'plugin:eslint-comments/recommended',
+    'prettier',
+  ],
+  plugins: ['eslint-comments', 'simple-import-sort', 'jest', 'jest-formatting'],
+  rules: {
+    'prefer-template': 'error',
+    'no-else-return': 'error',
+    '@typescript-eslint/no-explicit-any': 'off',
+    'eslint-comments/require-description': 'error',
+    'eslint-comments/disable-enable-pair': 'off',
+    'simple-import-sort/imports': 'error',
+    'simple-import-sort/exports': 'error',
+    'jest/prefer-expect-assertions': 'off',
+    'jest/require-hook': 'off',
+  },
+};

.gitattributes

@@ -0,0 +1 @@
+targets/http/http1.1/fixtures text

.gitignore

@@ -1,3 +1,4 @@
 *.log
 node_modules
 coverage*
+dist

.npmignore

@@ -1,2 +1,7 @@
-.editorconfig
-test
+# Ignore everything by default
+# NOTE: NPM publish will never ignore package.json, package-lock.json, README, LICENSE, CHANGELOG
+# https://npm.github.io/publishing-pkgs-docs/publishing/the-npmignore-file.html
+*
+
+# Don't ignore dist folder
+!dist/**

.prettierignore

@@ -0,0 +1,5 @@
+build
+node_modules
+src/targets/**/fixtures
+dist
+bin

.prettierrc.js

@@ -0,0 +1,16 @@
+/** @type { import('prettier').Config } */
+module.exports = {
+  arrowParens: 'avoid',
+  bracketSameLine: false,
+  bracketSpacing: true,
+  jsxSingleQuote: false,
+  printWidth: 100,
+  proseWrap: 'never',
+  quoteProps: 'as-needed',
+  semi: true,
+  singleAttributePerLine: true,
+  singleQuote: true,
+  tabWidth: 2,
+  trailingComma: 'all',
+  useTabs: false,
+};

.travis.yml

@@ -0,0 +1,3 @@
+{
+  "recommendations": ["EditorConfig.EditorConfig"]
+}

.vscode/extensions.json

@@ -0,0 +1,4 @@
+{
+  "files.insertFinalNewline": false, // controlled by the .editorconfig at root since we can't map vscode settings directly to files (see: https://github.com/microsoft/vscode/issues/35350)
+  "editor.defaultFormatter": "esbenp.prettier-vscode"
+}

.vscode/settings.json

@@ -1,139 +1,101 @@
 # Contributing to this project
 
-Please take a moment to review this document in order to make the contribution
-process easy and effective for everyone involved.
+Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
 
-Following these guidelines helps to communicate that you respect the time of
-the developers managing and developing this open source project. In return,
-they should reciprocate that respect in addressing your issue or assessing
-patches and features.
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
 
 ## Using the issue tracker
 
-The [issue tracker](/issues) is the preferred channel for [bug reports](#bug-reports),
-[features requests](#feature-requests) and [submitting pull requests](#pull-requests), 
-but please respect the following restrictions:
+The [issue tracker](/issues) is the preferred channel for [bug reports](#bug-reports), [features requests](#feature-requests) and [submitting pull requests](#pull-requests), but please respect the following restrictions:
 
-* Please **do not** use the issue tracker for personal support requests (use
-  [Stack Overflow](http://stackoverflow.com) or IRC).
+- Please **do not** use the issue tracker for personal support requests (use [Stack Overflow](http://stackoverflow.com) or IRC).
 
-* Please **do not** derail or troll issues. Keep the discussion on topic and
-  respect the opinions of others.
+- Please **do not** derail or troll issues. Keep the discussion on topic and respect the opinions of others.
 
 ## Bug reports
 
-A bug is a _demonstrable problem_ that is caused by the code in the repository.
-Good bug reports are extremely helpful - thank you!
+A bug is a _demonstrable problem_ that is caused by the code in the repository. Good bug reports are extremely helpful - thank you!
 
 Guidelines for bug reports:
 
-1. **Use the GitHub issue search** — check if the issue has already been
-    reported.
+1. **Use the GitHub issue search** — check if the issue has already been reported.
 
-2. **Check if the issue has been fixed** — try to reproduce it using the
-    latest `master` or development branch in the repository.
+2. **Check if the issue has been fixed** — try to reproduce it using the latest `master` or development branch in the repository.
 
-3. **Isolate the problem** — create a [reduced test
-    case](http://css-tricks.com/6263-reduced-test-cases/) and a live example.
+3. **Isolate the problem** — create a [reduced test case](http://css-tricks.com/6263-reduced-test-cases/) and a live example.
 
-A good bug report shouldn't leave others needing to chase you up for more
-information. Please try to be as detailed as possible in your report. What is
-your environment? What steps will reproduce the issue? What browser(s) and OS
-experience the problem? What would you expect to be the outcome? All these
-details will help people to fix any potential bugs.
+A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
 
 Example:
 
 > Short and descriptive example bug report title
 >
-> A summary of the issue and the browser/OS environment in which it occurs. If
-> suitable, include the steps required to reproduce the bug.
+> A summary of the issue and the browser/OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.
 >
 > 1. This is the first step
 > 2. This is the second step
 > 3. Further steps, etc.
 >
 > `<url>` - a link to the reduced test case
 >
-> Any other information you want to share that is relevant to the issue being
-> reported. This might include the lines of code that you have identified as
-> causing the bug, and potential solutions (and your opinions on their
-> merits).
+> Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).
 
 ## Feature requests
 
-Feature requests are welcome. But take a moment to find out whether your idea
-fits with the scope and aims of the project. It's up to *you* to make a strong
-case to convince the project's developers of the merits of this feature. Please
-provide as much detail and context as possible.
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to _you_ to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
 
 ## Pull requests
 
-Good pull requests (patches, improvements, new features) are a fantastic
-help. They should remain focused in scope and avoid containing unrelated
-commits.
+Good pull requests (patches, improvements, new features) are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
 
-**Please ask first** before embarking on any significant pull request (e.g.
-implementing features, refactoring code, porting to a different language),
-otherwise you risk spending a lot of time working on something that the
-project's developers might not want to merge into the project.
+**Please ask first** before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
 
-Please adhere to the coding conventions used throughout a project (indentation,
-accurate comments, etc.) and any other requirements (such as test coverage).
+Please adhere to the coding conventions used throughout a project (indentation, accurate comments, etc.) and any other requirements (such as test coverage).
 
-Follow this process if you'd like your work considered for inclusion in the
-project:
+Follow this process if you'd like your work considered for inclusion in the project:
 
-1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
-    and configure the remotes:
+1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork, and configure the remotes:
 
-    ```bash
-    # Clone your fork of the repo into the current directory
-    git clone https://github.com/<your-username>/<repo-name>
-    # Navigate to the newly cloned directory
-    cd <repo-name>
-    # Assign the original repo to a remote called "upstream"
-    git remote add upstream https://github.com/Mashape/httpsnippet.git
-    ```
+   ```bash
+   # Clone your fork of the repo into the current directory
+   git clone https://github.com/<your-username>/<repo-name>
+   # Navigate to the newly cloned directory
+   cd <repo-name>
+   # Assign the original repo to a remote called "upstream"
+   git remote add upstream https://github.com/Kong/httpsnippet.git
+   ```
 
 2. If you cloned a while ago, get the latest changes from upstream:
 
-    ```bash
-    git checkout <dev-branch>
-    git pull upstream <dev-branch>
-    ```
+   ```bash
+   git checkout <dev-branch>
+   git pull upstream <dev-branch>
+   ```
 
-3. Create a new topic branch (off the main project development branch) to
-    contain your feature, change, or fix:
+3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:
 
-    ```bash
-    git checkout -b <topic-branch-name>
-    ```
+   ```bash
+   git checkout -b <topic-branch-name>
+   ```
 
-4. Commit your changes in logical chunks. Please adhere to these [git commit
-    message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
-    or your code is unlikely be merged into the main project. Use Git's
-    [interactive rebase](https://help.github.com/articles/interactive-rebase)
-    feature to tidy up your commits before making them public.
+4. Commit your changes in logical chunks. Please adhere to these [git commit message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) or your code is unlikely be merged into the main project. Use Git's [interactive rebase](https://help.github.com/articles/interactive-rebase) feature to tidy up your commits before making them public.
 
 5. Locally merge (or rebase) the upstream development branch into your topic branch:
 
-    ```bash
-    git pull [--rebase] upstream <dev-branch>
-    ```
+   ```bash
+   git pull [--rebase] upstream <dev-branch>
+   ```
 
 6. Push your topic branch up to your fork:
 
-    ```bash
-    git push origin <topic-branch-name>
-    ```
+   ```bash
+   git push origin <topic-branch-name>
+   ```
 
-7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-    with a clear title and description.
+7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description.
 
-**IMPORTANT**: By submitting a patch, you agree to allow the project owner to
-license your work under the same license as that used by the project.
+**IMPORTANT**: By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by the project.
 
 ## Creating New Conversion Targets
 
-For a info on creating new conversion targets, please review this [guideline](https://github.com/Mashape/httpsnippet/wiki/Creating-Targets)
+For a info on creating new conversion targets, please review this [guideline](https://github.com/Kong/httpsnippet/wiki/Creating-Targets)

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015 Mashape (https://www.mashape.com)
+Copyright (c) 2022 Kong (https://www.konghq.com)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal