# result-type

> nothing but a Result type

Latest version **1.0.0** (published 2013-06-19) · MIT license · 0 weekly downloads

## Install

```sh
npm install result-type
pnpm add result-type
yarn add result-type
bun add result-type
```

## Health

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

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.0 |
| Published | 2013-06-19 |
| First published | 2013-06-19 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Jake Rosoman |
| Maintainers | jkroso |
| Keywords | result, type, spec |

## Links

- npm: https://www.npmjs.com/package/result-type
- Repository: https://github.com/jkroso/result-type
- Issues: https://github.com/jkroso/result-type/issues
- npm.io page: https://npm.io/package/result-type

## Alternatives

- [@openai/codex-sdk](https://npm.io/package/@openai/codex-sdk.md) — 731.4K weekly downloads
- [babel-plugin-transform-react-jsx](https://npm.io/package/babel-plugin-transform-react-jsx.md) — 565.0K weekly downloads
- [babel-helper-remove-or-void](https://npm.io/package/babel-helper-remove-or-void.md) — 508.5K weekly downloads
- [@pnpm/store-controller-types](https://npm.io/package/@pnpm/store-controller-types.md) — 186.9K weekly downloads
- [react-native-signature-canvas](https://npm.io/package/react-native-signature-canvas.md) — 155.6K weekly downloads

## Recent versions

- 1.0.0 (latest) — 2013-06-19

## README

# result-type

  Just an empty class to use as a kind of tag. If your implementing something you consider to be a "Result" you can inherit from it and enjoy nice reliable type detection via `instanceof`. This would normally be too limited but in the case of Result implementations should be fine. Its probably a bad idea anyway though since module systems like npm can easily duplicate modules but fuck it lets see if it works with better package managers.

## Installation

  This form of type checking relies on identity. That means every module that dependends on it must load the exact same path.

_With [component](//github.com/component/component)_  

	$ component install jkroso/result-type

_With [packin](//github.com/jkroso/packin)_  

	$ packin install result-type:http://github.com/jkroso/result-type/tarball/1.0.0

_With [npm](//github.com/isaacs/npm)_  

	$ echo "good luck" && npm install result-type

then in your app:

```js
inherit(MyResultClass, require('result-type'))
```

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