Skip to content

Releases: raveljs/ravel

Release 1.0.0-rc.3

24 Jul 21:01
5e23d4a
Compare
Choose a tag to compare
Release 1.0.0-rc.3 Pre-release
Pre-release
  • Added renaming support to @autoinject

Release 1.0.0-rc.2

24 Jul 15:30
0de5bc2
Compare
Choose a tag to compare
Release 1.0.0-rc.2 Pre-release
Pre-release
  • Addition of the @postinject decorator

Release 1.0.0-rc.1

21 Jun 20:18
57d755f
Compare
Choose a tag to compare
Release 1.0.0-rc.1 Pre-release
Pre-release

Ravel's first release candidate for 1.0.0!

A great deal of house-keeping and polishing has gone into this release, resulting in several (relatively minor) API-breaking changes primarily via #246. Please see the [Migration Guide](https://github.com/raveljs/ravel/wiki/Migration-Guide-(0.25.x----1.0.0-rc.x) for a full outline of changes and how to adapt your existing codebase to them.

There will likely be several release candidates before 1.0.0 is released, as feedback is gathered from existing teams/apps using Ravel. Stay tuned...

Release 0.25.0

26 Apr 01:43
a8ffb22
Compare
Choose a tag to compare
Release 0.25.0 Pre-release
Pre-release

Support for environment variable interpolation in .ravelrc.json via #238

Release 0.24.1

05 Apr 14:14
186232e
Compare
Choose a tag to compare
Release 0.24.1 Pre-release
Pre-release

Fix for #235

Release 0.24.0

02 Apr 20:24
94c8d94
Compare
Choose a tag to compare
Release 0.24.0 Pre-release
Pre-release
  • Introduction of the @middleware decorator: #228
  • Inclusion of an integrated in-memory redis mock to ease development. Horizontal scaling still requires a real redis server. #232

Release 0.23.0

01 Nov 20:58
2e27613
Compare
Choose a tag to compare
Release 0.23.0 Pre-release
Pre-release

This release contains async support for lifecycle decorators (see #221 for more information). It is now guaranteed that each lifecycle decorated method will finish execution before the next lifecycle event, even if that method returns a Promise. A consequence of this is that app.init() and app.listen() now return Promises and need to be used accordingly:

API changes:

app.js

// I would suggest using an IIFE for maximum flexibility
(async () => {
  await app.init();
  // do things in between (if you want), then listen.
  await app.listen();
})();

If you do not wait for .init() to finish before calling .listen(), then your app will fail to start. If you are using app.start(), it does this internally and there is no API change there.

Release 0.22.6

27 Oct 18:17
21aa323
Compare
Choose a tag to compare
Release 0.22.6 Pre-release
Pre-release
  • Addition of the @interval lifecycle decorator
  • Fix for #223

Release 0.22.5

20 Oct 03:25
e24960e
Compare
Choose a tag to compare
Release 0.22.5 Pre-release
Pre-release

Fix for #219

Release 0.22.4

20 Oct 02:47
09324e1
Compare
Choose a tag to compare
Release 0.22.4 Pre-release
Pre-release

Fix for #218