nock 11.3.6 → 11.7.0

package/package.json

@@ -7,7 +7,7 @@
     "testing",
     "isolation"
   ],
-  "version": "11.3.6",
+  "version": "11.7.0",
   "author": "Pedro Teixeira <pedro.teixeira@gmail.com>",
   "repository": {
     "type": "git",
@@ -31,28 +31,30 @@
   },
   "devDependencies": {
     "assert-rejects": "^1.0.0",
+    "dirty-chai": "^2.0.1",
     "dtslint": "^0.9.1",
     "eslint": "^6.0.0",
     "eslint-config-prettier": "^6.0.0",
     "eslint-config-standard": "^14.0.0",
     "eslint-plugin-import": "^2.16.0",
+    "eslint-plugin-mocha": "^6.2.0",
     "eslint-plugin-node": "^10.0.0",
     "eslint-plugin-promise": "^4.1.1",
     "eslint-plugin-standard": "^4.0.0",
     "got": "^9.6.0",
-    "hyperquest": "^2.1.3",
     "isomorphic-fetch": "^2.2.0",
-    "lolex": "^4.0.1",
+    "lolex": "^5.0.0",
+    "mocha": "^6.2.2",
     "needle": "^2.3.0",
     "npm-run-all": "^4.1.5",
     "nyc": "^14.0.0",
     "prettier": "1.18.2",
     "proxyquire": "^2.1.0",
     "request": "^2.83.0",
-    "restify-clients": "^2.2.0",
     "rimraf": "^3.0.0",
     "semantic-release": "^16.0.0-beta.22",
-    "sinon": "^7.3.1",
+    "sinon": "^7.5.0",
+    "sinon-chai": "^3.3.0",
     "superagent": "^5.0.2",
     "tap": "^14.0.0"
   },
@@ -62,6 +64,7 @@
     "test": "npm run -s unit",
     "posttest": "npm run -s prettier:check",
     "coverage": "tap --coverage-report=html && open coverage/lcov-report/index.html",
+    "mocha": "nyc mocha $(grep -lr '^\\s*it(' tests)",
     "lint": "eslint \"**/*.js\"",
     "prettier": "prettier --write \"**/*.@(js|json|md|ts|yml)\"",
     "prettier:check": "prettier --check \"**/*.@(js|json|md|ts|yml)\"",
@@ -77,5 +80,10 @@
       "tests/"
     ]
   },
-  "license": "MIT"
+  "license": "MIT",
+  "files": [
+    "index.js",
+    "lib",
+    "types/index.d.ts"
+  ]
 }

package/types/index.d.ts

@@ -26,6 +26,7 @@ declare namespace nock {
   function loadDefs(path: string): Definition[]
   function define(defs: Definition[]): Scope[]
   function restore(): void
+  function abortPendingRequests(): void
 
   let back: Back
   let emitter: NodeJS.EventEmitter
@@ -243,6 +244,7 @@ declare namespace nock {
   type BackMode = 'wild' | 'dryrun' | 'record' | 'lockdown'
 
   interface Back {
+    currentMode: BackMode
     fixtures: string
     setMode(mode: BackMode): void
 

package/.all-contributorsrc

@@ -1,123 +0,0 @@
-{
-  "projectName": "nock",
-  "projectOwner": "nock",
-  "repoType": "github",
-  "repoHost": "https://github.com",
-  "files": [
-    "README.md"
-  ],
-  "imageSize": 100,
-  "commit": false,
-  "contributors": [
-    {
-      "login": "pgte",
-      "name": "Pedro Teixeira",
-      "avatar_url": "https://avatars1.githubusercontent.com/u/47910?v=4",
-      "profile": "http://pgte.me",
-      "contributions": [
-        "code",
-        "maintenance"
-      ]
-    },
-    {
-      "login": "n30n0v",
-      "name": "n30n0v",
-      "avatar_url": "https://avatars3.githubusercontent.com/u/10771967?v=4",
-      "profile": "https://github.com/n30n0v",
-      "contributions": [
-        "code"
-      ]
-    },
-    {
-      "login": "RichardLitt",
-      "name": "Richard Littauer",
-      "avatar_url": "https://avatars3.githubusercontent.com/u/910753?v=4",
-      "profile": "https://burntfen.com",
-      "contributions": [
-        "maintenance",
-        "code",
-        "blog"
-      ]
-    },
-    {
-      "login": "ianwsperber",
-      "name": "Ian Walker-Sperber",
-      "avatar_url": "https://avatars1.githubusercontent.com/u/3731165?v=4",
-      "profile": "http://ianwsperber.com",
-      "contributions": [
-        "code"
-      ]
-    },
-    {
-      "login": "ierceg",
-      "name": "Ivan Erceg",
-      "avatar_url": "https://avatars2.githubusercontent.com/u/1505203?v=4",
-      "profile": "http://ilovacha.com",
-      "contributions": [
-        "code",
-        "maintenance"
-      ]
-    },
-    {
-      "login": "paulmelnikow",
-      "name": "Paul Melnikow",
-      "avatar_url": "https://avatars2.githubusercontent.com/u/1487036?v=4",
-      "profile": "https://twitter.com/paulmelnikow",
-      "contributions": [
-        "code",
-        "maintenance"
-      ]
-    },
-    {
-      "login": "gr2m",
-      "name": "Gregor Martynus",
-      "avatar_url": "https://avatars3.githubusercontent.com/u/39992?v=4",
-      "profile": "https://twitter.com/gr2m",
-      "contributions": [
-        "code",
-        "maintenance",
-        "business",
-        "financial",
-        "blog"
-      ]
-    },
-    {
-      "login": "hutson",
-      "name": "Hutson Betts",
-      "avatar_url": "https://avatars1.githubusercontent.com/u/6701030?v=4",
-      "profile": "https://gitlab.com/hutson",
-      "contributions": [
-        "financial"
-      ]
-    },
-    {
-      "login": "jlilja",
-      "name": "Jonas Lilja",
-      "avatar_url": "https://avatars2.githubusercontent.com/u/6105119?v=4",
-      "profile": "http://lilja.io",
-      "contributions": [
-        "financial",
-        "code"
-      ]
-    },
-    {
-      "login": "benrki",
-      "name": "Benjamin Ki",
-      "avatar_url": "https://avatars0.githubusercontent.com/u/4446950?v=4",
-      "profile": "https://github.com/benrki",
-      "contributions": [
-        "financial"
-      ]
-    },
-    {
-      "login": "chadfawcett",
-      "name": "Chad Fawcett",
-      "avatar_url": "https://avatars2.githubusercontent.com/u/3250463?v=4",
-      "profile": "http://chadf.ca",
-      "contributions": [
-        "financial"
-      ]
-    }
-  ],
-  "contributorsPerLine": 7
-}

package/.eslintignore

@@ -1,3 +0,0 @@
-/coverage
-/tests/browserify-public/browserify-bundle.js
-node_modules

package/.eslintrc.yml

@@ -1,34 +0,0 @@
-env:
-  node: true
-
-parserOptions:
-  ecmaVersion: 9
-  # Override eslint-config-standard, which incorrectly sets this to "module",
-  # though that setting is only for ES6 modules, not CommonJS modules.
-  sourceType: 'script'
-
-extends:
-  - 'eslint:recommended'
-  - standard
-  - prettier
-
-rules:
-  # TODO These are included in standard and should be cleaned up and turned on.
-  node/no-deprecated-api: 'off' # we still make heavy use of url.parse
-
-  # Nock additions.
-  strict: ['error', 'safe']
-  no-loop-func: 'error'
-  no-var: 'error'
-  prefer-const: 'error'
-  object-shorthand: ['error', 'properties']
-  prefer-template: 'error'
-  arrow-body-style: ['error', 'as-needed']
-  prefer-destructuring:
-    [
-      'error',
-      {
-        'VariableDeclarator': { 'array': false, 'object': true },
-        'AssignmentExpression': { 'array': false, 'object': false },
-      },
-    ]

package/.github/FUNDING.yml

@@ -1 +0,0 @@
-open_collective: nock

package/.github/ISSUE_TEMPLATE/01_bug_report.md

@@ -1,26 +0,0 @@
----
-name: 🐛 Bug report
-about: If something isn't working 🤕
----
-
-**What is the expected behavior?**
-
-**What is the actual behavior?**
-
-**Possible solution**
-
-**How to reproduce the issue**
-
-Runkit: _[Example link](https://runkit.com/gr2m/node-nock-nock-768)_
-
-_Having problem producing a test case? Try and ask the community for help. If the test case cannot be reproduced, the Nock community might not be able to help you._
-
-**Does the bug have a test case?**
-
-**Versions**
-
-| Software   | Version(s) |
-| ---------- | ---------- |
-| Nock       |            |
-| Node       |            |
-| TypeScript |            |

package/.github/ISSUE_TEMPLATE/02_feature_request.md

@@ -1,20 +0,0 @@
----
-name: 🚀 Feature request
-about: Let us know if you have a feature request 💡
----
-
-**Context**
-
-What are you trying to do and how would you want to do it differently? Is it something you currently you cannot do? Is this related to an issue/problem?
-
-**Alternatives**
-
-Can you achieve the same result doing it in an alternative way? Is the alternative considerable?
-
-**Has the feature been requested before?**
-
-Please provide a link to the issue.
-
-**If the feature request is accepted, would you be willing to submit a PR?**
-
-Yes / No _(Help can be provided if you need assistance submitting a PR)_

package/.github/ISSUE_TEMPLATE/03_support.md

@@ -1,10 +0,0 @@
----
-name: ❓ Support
-about: If you need support, check out Nock on StackOverflow
----
-
-<!--                 👆 Click "Preview" for a nicer view! -->
-
-We primarily use GitHub as an issue tracker; for usage and support questions we primairly use StackOverflow. Please tag the questions with `nock` so the community can easily find it. [Go to StackOverflow](https://stackoverflow.com/questions/tagged/nock).
-
-If you want to submit a feature request you can do that [here](https://github.com/nock/nock/issues/new?template=feature_request.md) or bug reports [here](https://github.com/nock/nock/issues/new?template=bug_report.md).

package/.github/ISSUE_TEMPLATE/04_thanks.md

@@ -1,20 +0,0 @@
----
-name: ❤️ Say thank you
-about: Tell us how you use nock & support our efforts in maintaining Nock
----
-
-# ❤️ I'm using Nock
-
-If you (or your company) are using Nock - please let us know. We'd love to hear from you!
-
-Nock is a community driven project, which means it's not maintained by a company. If you would like to help Nock - any of the following is greatly appreciated.
-
-- [ ] Give the repository a star ⭐️
-- [ ] Help out with issues
-- [ ] Review pull requests
-- [ ] Blog about Nock
-- [ ] Make tutorials
-- [ ] Give talks
-- [ ] Support us on [https://opencollective.com/nock](https://opencollective.com/nock)
-
-Thank you! 💐

package/.github/lock.yml

@@ -1,19 +0,0 @@
-# Configuration for lock-threads - https://github.com/dessant/lock-threads
-
-# Number of days of inactivity before a closed issue or pull request is locked
-daysUntilLock: 14
-
-# Issues and pull requests with these labels will not be locked. Set to `[]` to disable
-exemptLabels: []
-
-# Label to add before locking, such as `outdated`. Set to `false` to disable
-lockLabel: false
-
-# Comment to post before locking. Set to `false` to disable
-lockComment: >
-  This thread has been automatically locked since there has not been
-  any recent activity after it was closed. Please open a new issue and
-  add a reference to this one if it’s related. Thank you!
-
-# Assign `resolved` as the reason for locking. Set to `false` to disable
-setLockReason: true

package/.github/stale.yml

@@ -1,25 +0,0 @@
-# Configuration for probot-stale - https://github.com/probot/stale
-
-# Number of days of inactivity before an Issue or Pull Request becomes stale
-daysUntilStale: 90
-
-# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
-# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
-daysUntilClose: 7
-
-# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
-exemptLabels:
-  - pinned
-
-# Label to use when marking as stale
-staleLabel: stale
-
-# Comment to post when marking as stale. Set to `false` to disable
-markComment: >
-  This issue has been automatically marked as stale because it has not had
-  recent activity. It will be closed if no further activity occurs. We try to
-  do our best, but nock is maintained by volunteers and there is only so much
-  we can do at a time. Thank you for your contributions.
-
-# Limit the number of actions per hour, from 1-30. Default is 30
-limitPerRun: 30

package/.github/toc.yml

@@ -1 +0,0 @@
-bullets: '-'

package/.istanbul.yml

@@ -1,5 +0,0 @@
-instrumentation:
-  excludes: ['tests/**/*.js', 'examples/**/*.js', 'lib/recorder.js']
-check:
-  global:
-    lines: 90

package/.prettierignore

@@ -1,5 +0,0 @@
-package.json
-package-lock.json
-/.nyc_output
-/coverage
-/tests/browserify-public/browserify-bundle.js

package/.prettierrc.yml

@@ -1,4 +0,0 @@
-semi: false
-singleQuote: true
-trailingComma: es5
-bracketSpacing: true

package/.travis.yml

@@ -1,47 +0,0 @@
-language: node_js
-cache: npm
-
-# Trigger a push build on master and greenkeeper branches + PRs build on every branches
-# Avoid double build on PRs (See https://github.com/travis-ci/travis-ci/issues/1147)
-branches:
-  only:
-    - master
-    - /^greenkeeper.*$/
-    - beta # semantic-release preview releases
-    - next # semantic-release @next releases
-    - /^\d+\.x$/ # semantic-release maintenance releases
-
-stages:
-  - lint
-  - test
-  - name: release
-    if: branch =~ /^(\d+\.x|master|next|beta)$/ AND type IN (push)
-  - name: update-prettier
-    if: branch =~ ^greenkeeper/prettier
-
-jobs:
-  include:
-    - stage: update-prettier
-      node_js: lts/*
-      script:
-        - git checkout $TRAVIS_BRANCH
-        - npm run prettier
-        # commit changes and push back to branch on GitHub. If there are no changes then exit without error
-        - 'git commit -a -m "style: prettier" && git push "https://${GH_TOKEN}@github.com/$TRAVIS_REPO_SLUG" ${TRAVIS_BRANCH} || true'
-    - stage: lint
-      node_js: lts/*
-      env: linting
-      # Show prettier errors, even if lint fails.
-      script: run-s --silent --continue-on-error lint prettier:check dtslint
-    - stage: test
-      node_js: 12
-    - node_js: 10
-      # Avoid running lint and prettier again.
-      script: npm run --silent unit
-    - node_js: 8
-      # Avoid running lint and prettier again.
-      script: npm run --silent unit
-    - stage: release
-      node_js: lts/*
-      env: semantic-release
-      script: npm run semantic-release

package/CODE_OF_CONDUCT.md

@@ -1,46 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at nock+coc@martynus.net or coc+nock@maintainer.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

package/CONTRIBUTING.md

@@ -1,164 +0,0 @@
-# Contribute
-
-👋 Thanks for thinking about contributing to nock! We, the maintainers, are glad you're here and will be excited to help you get started if you have any questions. For now, here are some basic instructions for how we manage this project.
-
-Please note that this project is released with a [Contributor Code of Conduct](./CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
-
-**Table of Contents**
-
-<!-- toc -->
-
-- [Branching](#branching)
-  - [Backport a fix / feature to a previous version](#backport-a-fix--feature-to-a-previous-version)
-  - [Submit a Beta / Next release](#submit-a-beta--next-release)
-- [Formatting & linting](#formatting--linting)
-- [Commit Message conventions](#commit-message-conventions)
-- [Generate README TOC](#generate-readme-toc)
-- [Running tests](#running-tests)
-  - [Running only a single test](#running-only-a-single-test)
-- [Release Process](#release-process)
-- [GitHub Apps](#github-apps)
-- [Becoming a maintainer](#becoming-a-maintainer)
-- [Who is funding work on Nock?](#who-is-funding-work-on-nock)
-- [Priority Support](#priority-support)
-- [Is there a chat where I can talk to other maintainers and users?](#is-there-a-chat-where-i-can-talk-to-other-maintainers-and-users)
-
-<!-- tocstop -->
-
-## Branching
-
-**TLDR: Most pull requests should be opened against the `beta` branch.**
-
-We use [semantic-release](https://github.com/semantic-release/semantic-release) to automate the release of new versions based on semantic commit messages as described above. Depending on the branch that a new pull request is merged into, it is published to different versions using different [npm dist-tags](https://docs.npmjs.com/cli/dist-tag).
-
-- `master`: Publish with `@latest`, or if the commits have been merged into `next` branch before, update the `@latest` dist-tag to point at the new version
-- `next`: Publish with `@next`
-- `beta`: Publish to `X.0.0-beta.Y`, where `X` is the next breaking version and `Y` is number that gets increased with each release.
-- `[Version].x`: For example `10.x`, where `10` is the major release number. No breaking changes are allowed on this branch. Publishes fix/feature versions to `[Version]` using a `@release-@[version].x` release tag
-
-### Backport a fix / feature to a previous version
-
-If you want to **backport a fix** to version 10, and the last version released on version 10 is `10.0.4`, then you have to follow these steps
-
-1. Create the `[Version].x` branch unless it already exists. If you don’t have write access, ask one of the maintainers to do it for you. In this example, the command is `git checkout -b 10.x v10.0.4`.
-2. Push the branch to GitHub: `git push -u origin $(git symbolic-ref --short HEAD)`
-3. Create a new branch based on `10.x`
-4. Make your changes
-5. Submit the pull request against the `10.x` branch
-
-### Submit a Beta / Next release
-
-Create a new branch based off `beta` or `next`, depending on what you want. Make your changes and submit them to the same branches. If either `beta` or `next` is outdated, ask a maintainer to re-create them from `master`
-
-## Formatting & linting
-
-This project formats its source code using Prettier. The most enjoyable way to
-use Prettier is to let it format code for you when you save. You can [integrate
-it into your editor][integrate prettier].
-
-[integrate prettier]: https://prettier.io/docs/en/editors.html
-
-If you don't want to integrate with your editor, you can run `npm run prettier`
-instead.
-
-Semantic issues are checked with ESLint via `npm run lint`.
-
-## Commit Message conventions
-
-`nock` releases are automated using [semantic-release](https://github.com/semantic-release/semantic-release).
-To automatically calculate the correct version number as well as changelogs,
-three commit message conventions need to be followed
-
-- Commit bug fixes with `fix: ...` or `fix(scope): ...` prefix in commit subject
-- Commit new features with `feat: ...` or `feat(scope): ...` prefix in commit subject
-- Commit breaking changes by adding `BREAKING CHANGE:` in the commit body
-  (not the subject line)
-
-Other helpful conventions are
-
-- Commit test files with `test: ...` or `test(scope): ...` prefix
-- Commit changes to `package.json`, `.gitignore` and other meta files with
-  `chore(filename-without-ext): ...`
-- Commit changes to README files or comments with `docs: ...`
-- Code style changes with `style: standard`
-
-Don't stress this; if necessary the maintainers can fix commit message(s) of a pull request using the `squash & merge` button.
-
-## Generate README TOC
-
-Make sure to update the README's table of contents whenever you update the README using the following npm script.
-
-```
-$ npm run toc
-```
-
-## Running tests
-
-All of the tests work offline. None of them should hit the network.
-
-```
-$ npm test
-```
-
-### Running only a single test
-
-When you're writing a test for a specific purpose, it may be useful to only run that test. In order to do this, you can pass a `only` option as the second argument to the [`tap`](https://www.node-tap.org/) testrunner. For instance in `tests/example.js`, like so:
-
-```js
-test('description', { only: true }, t => {
-  // ...
-})
-```
-
-And then:
-
-```sh
-$ tap --only tests/example_file.js
-```
-
-## Release Process
-
-All of our releases are automated using [semantic-release](https://github.com/semantic-release/semantic-release). The commit messages pushed to the master branch trigger new releases. Semantic-release requires that commits follow certain conventions, [described above](#commit-message-conventions). semantic-release creates a GitHub release, adds release notes and publishes the new version to npm. This is why we do not store release notes in the [`CHANGELOG`](CHANGELOG.md) file - they're already on GitHub.
-
-We use @nockbot as a separate account for releases, because npm tokens cannot be scoped to a single package. This improves our security model in case of a data breach involving npm tokens. @nockbot's credentials were set up by @gr2m; contact him if for any reason you need to change this in the future.
-
-## GitHub Apps
-
-We use several GitHub apps to help maintain this repository. While we would like to address every issue and while we would like to be on hand to support every person, Nock is pretty much entirely volunteer run, and we simply don't have the time to do everything. Please don't be offended if an automated app posts in your issue! We're doing what we can with with we have.
-
-Currently, we use the [Stale](https://github.com/apps/stale) and [Lock](https://github.com/apps/lock) apps to mark old issues as stale, and to lock issues which have been closed to stop drive-by comments. You can see the configuration files for these in [.github/](.github).
-
-## Becoming a maintainer
-
-So you want to do more than file a bug or submit a PR? Awesome!
-
-Nock is actively interested in having more maintainers. That means that we would love to have you (yes, you) get more involved if you want to! We don't have strict tests that you need to pass to become a maintainer. Instead, all we want is to find people who are frequent contributors, understand what Nock does, and are eager to help make this tool better.
-
-Here are some things you can do today to actively show the Nock team that you're interested in helping out in the long term:
-
-- **Triage issues!** We have more issues than we have bandwidth to deal with. For some of these issues, there are no labels, no comments suggesting how the issue could be resolved, and no follow-up after months or years of silence. It would be great if the issues actively reflected the state of the project. Go through old issues and suggesting labels in comments, ask for more information, and generally help out with the resolution process. This would be a great help!
-- **Review PRs.** We have a lot of open PRs! Some of these are probably ready to merge, and some of them probably need more work. Any extra eyes on PRs are encouraged. Comment on code patterns you think need work, suggest extra tests, and let us know if a PR 'LGTM' ("looks good to me"). The more reviewers we have, the faster we can merge issues, the better this project becomes.
-- **Help out!** If someone files a bug and no one has responded yet, see if you can resolve it! Suggest PRs, or file them yourself. While most contributors are going to only be interested in their own bugs, great maintainers help out with other people's bugs. This is one of the best ways to become an expert at Nock (and Node.js, JavaScript, or pretty much any project) - helping others.
-- **Write docs.** Are our docs missing something important? Are they not clear? Could they be better? Open a PR!
-- **Suggest examples.** Right now, we have a few examples, but we could always have more. Submit small example files and tutorials. At some point, we'll have to work on a better way to display these - for now, it's great to show others how to solve difficult mocking problems easily with Nock.
-- **Refactor.** This is one of the hardest things to do, but one of the most useful. Go through the code, and find examples where it could be written better - with better variable names, more useful abstractions, and more elegant patterns. Taking away ten lines of code that are unnecessary is more valuable than submitting a hundred new lines, sometimes. Open a PR or a comment and defend your position; ask for feedback.
-
-Once you've been around for a bit, ask a current Maintainer - one of [the team members](https://github.com/orgs/nock/people) - whether you can be elevated to Maintainer status and given permissions to close issues and merge PRs. We're interested in how well you know what Nock is about, and how involved you are in the community - not where you're from, how good your English is, or whether or not you can pass a whiteboard test blindfolded. If you think that you've been helpful, let us know. We're friendly, promise. :)
-
-## Who is funding work on Nock?
-
-Nock is entirely self-funded by [our Open Collective](https://opencollective.com/nock). Open Collective allows us to get contributions from users and companies, without giving away our open source IP. Think of it like a kickstarter, or an old-fashioned system of art patrons.
-
-If you'd like to give money to support Nock, please do go to our profile and check it out.
-
-## Priority Support
-
-As part of backing on Open Collective, we tag some issues as a priority if the user who opens them is also a backer, using the [Open Collective Bot](https://github.com/marketplace/open-collective-bot). In general, as maintainers we will give priority to support people who are working on these issues. The money in the Open Collective goes to the entire project, however, and maintainers are volunteers.
-
-## Is there a chat where I can talk to other maintainers and users?
-
-We don't have a chat for a variety of reasons - mainly, because our maintainers' time is limited, and we don't want to be on the hook for enforcing codes of conduct or for checking in every day. However, we encourage you to open issues about anything related to Nock! Issues really are the best way to keep the conversation focused on development.
-
-We often have video calls to pair program or to hack together on Nock. Join us! Look at the issues for a notification about these, and, if there isn't one planned, open an issue and suggest one.
-
-On that note, thanks for reading this far. Go mock some tests now, there's nothing left to read here. :)

package/assets/reply_file_1.txt

@@ -1 +0,0 @@
-Hello from the file!