Skip to content
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.

Releases: reno-router/reno

Bumps Deno to 1.7.2 and std to 0.86.0

09 Feb 09:49
Compare
Choose a tag to compare

Bumps Deno to 1.7.2 and std to 0.86.0

Exports ServerRequest from std/http version used by Reno

23 Dec 12:35
Compare
Choose a tag to compare

Exports ServerRequest from std/http version used by Reno; you most likely won't need to use this, but it resolves an issue within denosaurs/bench.

Bumps Deno to 1.6.0 and std to 0.80.0

18 Dec 13:14
Compare
Choose a tag to compare

Bumps Deno to 1.6.0 and std to 0.80.0.

Bumps Deno to 1.6.0 and std to 0.80.0

12 Dec 11:58
Compare
Choose a tag to compare

Bumps Deno to 1.6.0 and std to 0.80.0, and migrates CI pipeline to GitHub Actions as Travis CI's queue times are becoming unbearable.

Upgrades Deno 1.5.4 & std 0.79.0

28 Nov 18:33
Compare
Choose a tag to compare
  • Upgrades Deno to 1.5.4
  • Upgrades std to 0.79.0
  • Uses explicit export type statements for exporting types as required by Deno's use --isolatedModules TS flag
  • Fixes linting issues (mostly removing redunant async keyword usage)

Adds composition example to README

22 Oct 17:36
Compare
Choose a tag to compare

Adds a composition example to the README. Just publishing this so it propagates onto deno.land.

Upgrades Deno & std and migrates E2E tests to SuperDeno

17 Oct 16:22
Compare
Choose a tag to compare
  • Upgrades Deno to 1.4.6
  • Upgrades std to 0.74
  • Migrates end-to-end tests to SuperDeno, completely removing this project's dependency upon Node.js

Upgrades to Deno v1.4.2 + std@0.71

28 Sep 21:22
Compare
Choose a tag to compare
v1.3.2

Merge branch 'master' of github.com:reno-router/reno

Upgrades to Deno v1.3.3 + std@0.68

04 Sep 20:26
Compare
Choose a tag to compare

Includes the resolution of linting errors introduced by this upgrade.

Adds optional status code parameter to response helpers

16 Aug 15:28
Compare
Choose a tag to compare

Adds optional status code parameter to jsonResponse and textResponse, allowing a customer HTTP status to be set:

function methodNotAllowed(url: string, method: string) {
  return textResponse(`Method ${method} not allowed for ${url}`, {}, 405);
}

Note that this is fundamentally a breaking change. While upgrading to this version from 1.2.4 should be straightforward, you'll have to update any call sites where you're using these helpers to extend an object that already has a status property e.g:

return {
  // 'status' is specified more than once, so this usage will be overwritten. ts(2783)
  status: 201,
  ...textResponse("Created resource"),
};