sleepy-serv 0.1.1 → 0.1.3

package/README.md

@@ -0,0 +1,271 @@
+# Sleepy Server
+
+A directory-driven web server designed for REST-ful applications
+
+## Important Notes
+
+- This package requires [`bun.sh`](https://bun.sh) instead of NodeJS to run.
+- This project requires bun v1.2.3 or higher
+
+## Getting Started
+
+Here's a minimalist example on how to create a sleepy-serv app:
+
+```js
+import {
+  middleware,
+  createApp,
+} from 'sleepy-serv'
+
+const PORT = 3000
+
+const app = await createApp(PORT, import.meta.dirname)
+```
+
+The parameter for `import.meta.dirname` can be any directory you prefer, but it's common to point to the same directory as your root `index.js` file. The next step is to create an `/api` directory in the directory that you point to, and begin adding routes.
+
+### Return Value
+
+`sleepy-serv` was originally built for NodeJS, but it was ported to `bun` recently (before the initial release). The `createApp()` function merely calls `Bun.serve()` under-the-hood, and returns the `app` object that contains two properties:
+- `routes`: Contains a list of all of the routes defined by the file structure. This is useful for debugging.
+- `server`: this is the object that's returned from `Bun.serve()`. The `server` object has an `async` `.stop()` method on it, which can also be used for graceful shutdowns.
+
+### Adding Routes
+
+Routes are made up as _resources_ and _methods_. Resources are described by a directory path, and methods are described by files created inside of those directories. Resource segments can also represent dynamic routing params by starting the directory name with a colon (`:`).
+
+Here's file structure example:
+
+```
+/src
+  index.js # this is where we called `createApp()`
+  /api
+    /users
+      get.js
+      post.js
+      /:userId
+        get.js
+        delete.js
+        put.js
+```
+
+The file structure above create the following routes:
+
+- `GET /users`
+- `POST /users`
+- `GET /users/:userId`
+- `DELETE /users/:userId`
+- `PUT /users/:userId`
+
+These methods are supported:
+
+- GET
+- HEAD
+- PATCH
+- POST
+- PUT
+- DELETE
+
+### Method Definition Files
+
+The route's logic is implemented in the route definition files. These must `export default` either a function, or an array of functions for middleware purposes. The function signature takes a `BunRequest` object, and must return a `BunResponse` object.
+
+Here's an example of a simple handler function:
+
+```js
+export default function (req) {
+  return Response('Hello world')
+}
+```
+
+These handlers can also be `async` functions and `sleepy-serv` will wait for them to finish before moving on.
+
+### Middleware
+
+As mentioned earlier, method definition files can also export an array of functions:
+
+```js
+export default [
+  async req => {
+    req.parsedBody = await req.json()
+  },
+  req => {
+    console.log('JSON body:', req.parsedBody)
+
+    return new Response('Hello world', )
+  },
+]
+```
+
+This is useful if you want to break common logic up into reusable functions. The functions in the array are called in-order, and are provided the same `req` object. If you'd like to cache results between middleware functions, you can simply attach them to the `req` object.
+
+### Breaking the Middleware Chain - Responses
+
+You might want to break the middleware chain with a response early.
+
+Here's an example:
+
+```js
+export default [
+  req => {
+    if (req.params.userId === '123') {
+      return new Response('Returned early')
+    }
+  },
+  req => {
+    return new Response('End of chain')
+  },
+]
+```
+
+The the case above, the 1st middleware function will return a `Response` object if the route param's `userId` is equal to a specific value. In those cases, the last function in the middleware chain will not execute for that request.
+
+### Breaking the Middleware Chain - Errors
+
+It's also common to throw errors for things like request validation or when a desired resource is not found. `sleepy-serv` has defined custom `Error` types for every type of 4xx and 5xx error:
+
+```js
+import { NotFoundError } from 'sleepy-serv'
+
+export default async function (req) {
+  const users = await sql`
+SELECT * FROM Users
+WHERE userId=${req.params.userId}
+  `.trim()
+
+  const foundUser = users[0]
+
+  if (foundUser) {
+    return new Response.json(foundUser)
+  } else {
+    throw new NotFoundError()
+  }
+}
+```
+
+If the user is found in the database, then the request will return with a successful response containing the user's data. If the user is not found, then the `NotFoundError()` is thrown which will automatically respond with a _404 NotFound_ error.
+
+Throwing generic errors also works too:
+
+```js
+export default async function (req) {
+  throw new Error('A problem occurred')
+}
+```
+
+`sleepy-serv` will automatically respond with a _500 InternalServerError_ for any error types that aren't part of the `sleepy-serv` package.
+
+## Metadata Modules
+
+It's also possible for resource directories to contain a `meta.js` file. These files can export various things that have some sort semantic relationship to the part of the route that they're defined in.
+
+### Directory-Level Middleware
+
+`meta.js` files can also export an array of middleware functions:
+
+```js
+// meta.js
+
+export const middleware = [
+  req => { /* do middleware things */ },
+]
+```
+
+This middleware will be applied to all sibling and descendent method definition files within that directory.
+
+For example:
+
+```
+/src
+  index.js
+  /api
+    meta.js # metadata
+    get.js
+    /users
+      meta.js # metadata
+      get.js
+      post.js
+      /:userId
+        meta.js # metadata
+        get.js
+        delete.js
+        put.js
+```
+
+The middleware defined in `/api/meta.js` will be applied the following routes:
+
+- `GET /`
+- `GET /users`
+- `POST /users`
+- `GET /users/:userId`
+- `DELETE /users/:userId`
+- `PUT /users/:userId`
+
+The middleware defined in `/api/users/meta.js` will be applied the following routes:
+
+- `GET /users`
+- `POST /users`
+- `GET /users/:userId`
+- `DELETE /users/:userId`
+- `PUT /users/:userId`
+
+The middleware defined in `/api/users/:userId/meta.js` will be applied the following routes:
+
+- `GET /users/:userId`
+- `DELETE /users/:userId`
+- `PUT /users/:userId`
+
+### Future Use-Cases
+
+At the time of this writing, `meta.js` only exports middleware functions.
+
+## `createApp()` Options
+
+### `mountPath`
+
+This adds a prefix to all routes. For example:
+
+```js
+createApp(import.meta.dirname, {
+  mountPath: 'api/public',
+})
+```
+
+With the directory structure
+
+```
+/src
+  index.js # createApp()
+  /api
+    get.js
+    /users
+      get.js
+      post.js
+```
+
+Yields these routes:
+
+- `GET /api/public`
+- `GET /api/public/users`
+- `POST /api/public/users`
+
+### `onClose`
+
+When the app is started, the app can be shutdown gracefully by pressing Ctrl+D in the terminal. The `onClose` hook will be called during that shutdown if it's defined. `onClose` can also be `async` as well.
+
+```js
+const app = await createApp(PORT, import.meta.dirname, {
+  onClose: () => console.info('closing down...'),
+})
+```
+
+## Running the Local Example App
+
+1. Install [`bun.sh`](https://bun.sh)
+1. Link the library package:
+    - `$ cd lib`
+    - `$ bun link`
+1. Link the library to the project
+    - `$ cd ../example`
+    - `$ npm link sleepy-serv`
+1. Finally, run the app: `$ bun --watch run start`

package/package.json

@@ -2,7 +2,7 @@
   "name": "sleepy-serv",
   "description": "A more opinionated web server for building REST-ful applications",
   "author": "Travis J True",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "exports": "./src/index.js",
   "type": "module",
   "keywords": [
@@ -23,4 +23,4 @@
     "ajv": "^8.17.1",
     "ajv-formats": "^3.0.1"
   }
-}
+}