/test/deps.ts | superoak@4.8.1

import * as superoak from "https://deno.land/x/superoak@4.8.1/test/deps.ts";

A middleware framework for handling HTTP with Deno.

oak works well on both Deno CLI and Deno deploy, and is inspired by koa. It works well with both the Deno CLI and Deno Deploy.

Example server

A minimal router server which responds with content on /. With Deno CLI this will listen on port 8080 and on Deploy, this will simply serve requests received on the application.

import { Application, Router } from "https://deno.land/x/oak/mod.ts";

const router = new Router();
router.get("/", (ctx) => {
  ctx.response.body = `<!DOCTYPE html>
    <html>
      <head><title>Hello oak!</title><head>
      <body>
        <h1>Hello oak!</h1>
      </body>
    </html>
  `;
});

const app = new Application();
app.use(router.routes());
app.use(router.allowedMethods());

app.listen({ port: 8080 });

Namespaces

N etag	A collection of oak specific APIs for management of ETags.
N helpers	A collection of APIs to help assist in creating middleware.
N testing	A collection of utility APIs which can make testing of an oak application easier.

Classes

c Application	A class which registers middleware (via `.use()`) and then processes inbound requests against that middleware (via `.listen()`).
c Context	Provides context about the current request and response to middleware functions, and the current instance being processed is the first argument provided a `Middleware` function.
c Cookies deprecated	Provides an way to manage cookies in a request and response on the server as a single iterable collection, as well as the ability to sign and verify cookies to prevent tampering.
c FormDataReader	An interface which provides an interface to access the fields of a `multipart/form-data` body.
c HttpError	The base class that all derivative HTTP extend, providing a `status` and an `expose` property.
c HttpServerNative	The oak abstraction of the Deno native HTTP server which is used internally for handling native HTTP requests. Generally users of oak do not need to worry about this class.
c MultiPartStream	A class that takes a file (either a Deno.FsFile or Uint8Array) and bytes and streams the ranges as a multi-part encoded HTTP body.
c NativeRequest	An internal oak abstraction for handling a Deno native request. Most users of oak do not need to worry about this abstraction.
c Request	An interface which provides information about the current request. The instance related to the current request is available on the `Context`'s `.request` property.
c Response	An interface to control what response will be sent when the middleware finishes processing the request.
c Router	An interface for registering middleware that will run when certain HTTP methods and paths are requested, as well as provides a way to parameterize parts of the requested path.
c ServerSentEvent	An event which contains information which will be sent to the remote connection and be made available in an `EventSource` as an event. A server creates new events and dispatches them on the target which will then be sent to a client.

Enums

Status

Standard HTTP status codes.

Variables

v httpErrors	A namespace that contains each error constructor. Each error extends `HTTPError` and provides `.status` and `.expose` properties, where the `.status` will be an error `Status` value and `.expose` indicates if information, like a stack trace, should be shared in the response.
v REDIRECT_BACK	A symbol that indicates to `response.redirect()` to attempt to redirect back to the request referrer. For example:
v STATUS_TEXT	A record of all the status codes text.
v testing.mockContextState	Allows external parties to modify the context state.

Functions

f composeMiddleware	Compose multiple middleware functions into a single middleware function.
f createHttpError	A factory function which provides a way to create errors. It takes up to 3 arguments, the error `Status`, an message, which defaults to the status text and error options, which includes the `expose` property to set the `.expose` value on the error.
f dirname	Return the directory path of a `path`.
f etag.calculate	Calculate an ETag for an entity. When the entity is a specific set of data it will be fingerprinted as a "strong" tag, otherwise if it is just file information, it will be calculated as a weak tag.
f etag.factory	Create middleware that will attempt to decode the response.body into something that can be used to generate an `ETag` and add the `ETag` header to the response.
f etag.getEntity	For a given Context, try to determine the response body entity that an ETag can be calculated from.
f etag.ifMatch	A helper function that takes the value from the `If-Match` header and a calculated etag for the target. By using strong comparison, return `true` if the values match, otherwise `false`.
f etag.ifNoneMatch	A helper function that takes the value from the `If-None-Match` header and a calculated etag for the target entity and returns `false` if the etag for the entity matches the supplied value, otherwise `true`.
f expect
f helpers.getQuery	Given a context, return the `.request.url.searchParams` as a `Map` of keys and values of the params.
f ifRange	Determine, by the value of an `If-Range` header, if a `Range` header should be applied to a request, returning `true` if it should or otherwise `false`.
f isErrorStatus	A type guard that determines if the status code is an error.
f isFreePort	Determine if a port is available for using Requires `--allow-net` flag
f isHttpError	A type guard that determines if the value is an HttpError or not.
f isRedirectStatus	A type guard that determines if the status code is a redirection.
f join	Join all given a sequence of `paths`,then normalizes the resulting path.
f parseRange
f proxy	Middleware that provides a back-to-back proxy for requests.
f send	Asynchronously fulfill a response with a file from the local file system.
f testing.createMockApp	Creates a mock of `Application`.
f testing.createMockContext	Create a mock of `Context` or `RouterContext`.
f testing.createMockNext	Creates a mock `next()` function which can be used when calling middleware.

Interfaces

I ApplicationOptions	Available options that are used when creating a new instance of `Application`.
I BodyContentTypes
I BodyOptions	Options which can be used when accessing the `.body()` of a request.
I BodyOptionsContentTypes	When setting the `contentTypes` property of `BodyOptions`, provide additional content types which can influence how the body is decoded. This is specifically designed to allow a server to support custom or specialized media types that are not part of the public database.
I ByteRange
I ContextSendOptions
I CookiesGetOptions deprecated
I CookiesSetDeleteOptions deprecated
I etag.ETagOptions
I etag.FileInfo	Just the part of `Deno.FileInfo` that is required to calculate an `ETag`, so partial or user generated file information can be passed.
I FormDataBody	When reading a body in full via `.read()` from a `FormDataReader` this is what is what the value is resolved, providing a split between any fields, and multi-part files that were provided.
I FormDataFile	A representation of a file that has been read from a form data body. Based on the `FormDataReadOptions` that were passed when reading will determine if files are written to disk or not and how they are written to disk. When written to disk, the extension of the file will be determined by the content type, with the `.filename` property containing the full path to the file.
I FormDataReadOptions	Options which impact how the form data is decoded for a `FormDataReader`. All these options have sensible defaults for most applications, but can be modified for different use cases. Many of these options can have an impact on the stability of a server, especially if there is someone attempting a denial of service attack on your server, so be careful when changing the defaults.
I ListenOptionsBase
I ListenOptionsTls
I Middleware	Middleware are functions which are chained together to deal with requests.
I MiddlewareObject	Middleware objects allow encapsulation of middleware along with the ability to initialize the middleware upon listen.
I ProxyOptions
I Route
I RouterAllowedMethodsOptions
I RouterContext	The context passed router middleware.
I RouterMiddleware
I RouterOptions
I RouterParamMiddleware	Middleware that will be called by the router when handling a specific parameter, which the middleware will be called when a request matches the route parameter.
I SendOptions
I ServerConstructor
I ServerSentEventInit
I ServerSentEventTarget
I testing.MockContextOptions	Options that can be set in a mock context.

Type Aliases

T BodyBytes	The tagged type for `"bytes"` bodies.
T BodyForm	The tagged type for `"form"` bodies.
T BodyFormData	The tagged type for `"form-data"` bodies.
T BodyJson	The tagged type for `"json"` bodies.
T BodyReader	The tagged type for `"reader"` bodies.
T BodyStream	The tagged type for `"stream"` bodies.
T BodyText	The tagged type for `"text"` bodies.
T BodyType	The type of the body, where:
T BodyUndefined	The tagged type for `"undefined"` bodies.
T ErrorStatus	An HTTP status that is an error (4XX and 5XX).
T helpers.GetParamsOptions
T HTTPMethods	A type representing string literals of each of the common HTTP method.
T ListenOptions
T MiddlewareOrMiddlewareObject	Type that represents `Middleware` or `MiddlewareObject`.
T Next	A function for chaining middleware.
T RedirectStatus	An HTTP status that is a redirect (3XX).
T RouteParams
T State