# shauns-server

> A simple package that uses express to create more readable apps

Latest version **1.0.1** (published 2017-04-25) · ISC license · 0 weekly downloads

## Install

```sh
npm install shauns-server
pnpm add shauns-server
yarn add shauns-server
bun add shauns-server
```

## 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.1 |
| Published | 2017-04-25 |
| First published | 2017-04-18 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 3 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Shaun Wassell |
| Maintainers | shaunphil |

## Links

- npm: https://www.npmjs.com/package/shauns-server
- npm.io page: https://npm.io/package/shauns-server

## Dependencies (3)

- [lodash](https://npm.io/package/lodash.md) ^4.17.4
- [express](https://npm.io/package/express.md) ^4.15.2
- [body-parser](https://npm.io/package/body-parser.md) ^1.17.1

## Recent versions

- 1.0.1 (latest) — 2017-04-25
- 1.0.0 — 2017-04-18

## README

I noticed that we were using a lot of the same patterns when creating a backend for our apps, and that the code for these got really messy really fast.
So what I decided to do was start a small codebase that incorporated these patterns.
In this way, we can start setting up backends more quickly and deal with less bugs.
There's a lot of functionality I'd still like to add, such as a one-off pattern for REST APIs, automatic parameter resolution, etc.

The routes object should have the following structure:

const routes = [{
  segment: "api",
  get:     someAction,
  post:    someOtherAction,
  put:     yetAnotherAction,
  ...
  subroutes: [ ... ]
}, 

...

]

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