v3.0.0-rc.3

What's new?

• @marblejs/core - route builder - allowed to put r.applyMeta on top of pipe chain #226

Resolved issues

• @marblejs/middleware-multipart - middleware hangs if only files or only fields are provided #224
  (closes: #186)

Breaking changes:

• @marblejs/core/websockets/messaging - removed named listeners from server factory functions #225

v3.0.0-rc.2

What's new?

• @marblejs/messaging - added LocalStrategy together with injectable EventBus
• @marblejs/messaging - added reply utility function for event routing purposes
• @marblejs/middleware-multipart - internal code improvements
• @marblejs/core - added missing logging for error and close events

Resolved issues

• all: corrected logs formatting for undefined values
• resolved - ServerEvent.close never gets called #175

v3.0.0-rc.1

Before you'll read

• Marble.js v3 is currently in pre-release stage. Its API can change in the meantime while reaching the desired 3.0.0 version.
• New, up to date marblejs.com documentation for Marble.js v3 will land just before official release.
• Reach /packages/@integration for more detailed use cases and implementation examples

Whats new?

• support for TypeScript v3.7.x
• support forRxJS v6.5.x
• support for fp-ts v2.1.x
• Introducing new module @marblejs/messaging
• @marblejs/core - useContext utility function #184
• @marblejs/core - async readers #198
• @marblejs/core - injectable Logger reader #212
• @marblejs/core - improved server/context bootstrapping logging #212
• @marblejs/core - route resolving optimization (increased performance)
• @marblejs/core - uniform Listener interface
• @marblejs/core - injectable Http request bus #211
• @marblejs/core - route metadata are properly provided to routing table
• @marblejs/core - new feature - continuous request streams
• @marblejs/core - new feature - eagerly bootstrapped effects
• @marblejs/websockets - new feature - eagerly bootstrapped effects
• @marblejs/websockets - new feature - unified server creation (createWebSocketServer)
• @marblejs/websockets - refactor - event processing
• @marblejs/websockets - integration with injectable Logger reader #214
• @marblejs/websockets - default input/output event loggers
• ...and many many more internal refactors and optimizations

Breaking changes

• @marblejs/middleware-logger - removed deprecated loggerWithOpts$
• please see #172 for complete list of changes and API improvements

v2.3.1

Fixes

• @marblejs/middleware-multipart - fixed an issue when the middleware stream is resolved too early when the stream handler is attached (#151)

v2.3.0

What's new?

• @marblejs/middleware-multipart - a multipart/form-data middleware based on busboy library.

v2.2.3

What's new?

• @marblejs/core - Added ability to apply req/res metadata in testing mode (#141)

Fixes

• @marblejs/core - Body is not stringified when it's a stream, regardless of Content-Type header (#137)
• @marblejs/core - Query parameter ending on '.com' or similar doesn’t return 500 error (#147) (closes: #145 )
• @marblejs/core/+internal - Simplified createHttpRequest function and it's usages (#140)

v2.2.2

Fixes

• @marblejs/middleware-logger: changed LoggerOptions.stream type from fs.WritableStream into WritableLike

v2.2.0

Whats new?

• @marblejs/core: access server event stream via Context serverEvent$ token #128

Fixes

• @marblejs/core: lazy reader dependencies are bootstrapped only once (during initial context ask) #129
• @marblejs/websockets: incoming WebSocket connection is validated via verifyClient hook, just before the initial handshake #133
• @marblejs/middleware-io: requestValidator$ can update decoded values #132 (closes: #131
• all - set RxJS peer dependencies to minor version

v2.1.1

Whats new?

• @marblejs/core: added more HTTP statuses #123 (closes: #121)
• @marblejs/core: ability to grab the initial request from HTTP output$ via EffectMetadata.initiator #124 (closes: #122)

const output$: HttpOutputEffect = (res$, _, { initiator }) =>
  res$.pipe(
    // do something with response
  );

Fixes

• @marblejs/core: response.handler improved way how Node.js streams are detected #125

v2.1.0

Whats new?

• @marblejs/core: added support for passing Node.js streams into HttpEffectResponse body #116 (closes: #114)
• @marblejs/middleware-cors: introducing the new middleware that can be used to enable CORS with various options #100 (author: @Edouardbozon) 👏🎉
• @marblejs/middleware-logger: filter can handle incoming requests and outgoing responses #117 (closes: #115)