# appeared-a-wild

> Define code that should run when instances of various other modules appear

Latest version **0.9.0** (published 2018-03-28) · 0 weekly downloads

## Install

```sh
npm install appeared-a-wild
pnpm add appeared-a-wild
yarn add appeared-a-wild
bun add appeared-a-wild
```

## Health

**Score 10/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; low quality score; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.9.0 |
| Published | 2018-03-28 |
| First published | 2018-02-11 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 4.1 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Maintainers | erikpukinskis |

## Links

- npm: https://www.npmjs.com/package/appeared-a-wild
- Repository: https://github.com/erikpukinskis/appeared-a-wild
- Homepage: https://github.com/erikpukinskis/appeared-a-wild#readme
- Issues: https://github.com/erikpukinskis/appeared-a-wild/issues
- npm.io page: https://npm.io/package/appeared-a-wild

## Recent versions

- 0.9.0 (latest) — 2018-03-28
- 0.8.0 — 2018-02-11
- 0.7.0 — 2018-02-11
- 0.6.0 — 2018-02-11
- 0.5.0 — 2018-02-11
- 0.4.0 — 2018-02-11

## README

With appeared-a-wild you can register handlers for whatever _instances_ some specified module might throw at you.

For example, if you have a "WebSite" module, which you instantiate by calling `var site = new WebSite` then **appeared-a-wild** will let you sort of register to be notified when one of those appears:

```javascript
appearedAWild(
  ["release-checklist", "web-site"],
  function buildSite(list, site) {
    site.addRoute("get", "/housing-bond", function(request, response) {
      renderList(list, response)
    })
  }
)
```

Then whenever you declare those instances, your handler will be called:

```javascript
var WebSite = require("web-site")
var site = new WebSite()
appearedAWild.module(
  "web-site",
  function() { return site }
)

var releaseChecklist = require("release-checklist")
var list = releaseChecklist.get("test")
appearedAWild.module(
  "release-checklist",
  function() { return list }
)
```

At that point, `buildSite` will get called with `site` and `list`.

### Why

Typical node programs are designed to be started from the command line. You have "root" access to some machine, you `require("express")`, you hit some external ports, you grab stuff from the filesystem, etc.

Appeared-a-wild allows you to define hooks to those resources, without necessarily having instances of those resources yet. So that regardless of where that resource might come from... either a site that got started on a local UNIX port, or a site that is getting broadcasted into the browser, our code can just register that it's ready to work with that resource, wherever it might come from.

You can think of it as a commonjs-like namespace for *instances* rather than singletons. Which runs on top of commonjs's interface for defining singletons.

---
_Source: https://npm.io/package/appeared-a-wild · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._