2.0.0-rc2

• support exported array of route handlers
• support exported array of middleware funcs

2.0.0-rc1

Merge pull request #13 from ConjureLabs/v2

V2

1.2.0

Patches

• Changed to supporting .routes.json (not routes.json) for resolved config
• Added support for .routes.js config

1.1.0

Features

Direct function exports

When using crawSync you can now export functions directly.

module.exports = (req, res) => res.send('works')

Or an array of handlers

const handlers = []
handlers.push((req, res, next) => {
  req.asdf = 123
  next()
})
handlers.push((req, res) => {
  res.send(req.asdf) // '123'
})
module.exports = handlers

Resolved configuration jsons

Another feature added to syncCrawl is support for saving route configs in .json files, which are resolved as files as crawled.

.
└── routes
    ├─── routes.json             # { a: 123 }
    ├─── account                 # resolves { a: 123 }
    │   ├── routes.json          # { b: 456 }
    │   ├── get.js               # resolves { a: 123, b: 456 }
    └── get.js                   # resolves { a: 123 }

Inline config (direct in a Route constructor) overrides any resolved values.

Patches

• bumped dependencies
• some general housekeeping
• restricting node engine to 12.x.x
• added an examples directory

1.1.0-rc1

Merge pull request #10 from ConjureLabs/dont-always-need-Route

Allow exporting direct functions

1.0.0

release 1.0.0

0.8.1

Patches

• Fixed bug where multiple wildcard routes, in same dir, would splice out eachother

0.8.0

Features

• custom file handling now receives a second context argument

0.7.0

Features

• fileHandler option for route crawling, to handle fallback file processing

Changes

• custom verb filename handling now must be passed as verbs in the options hash (rather than a straight second argument)

0.6.1

Patches

• Fixed issue with filename matching expression