v2.4.1

• fix: aws-sdk v3 returns Uint8Array Payload from Lambda.invoke() e2913a6

v2.4.0...v2.4.1

v2.4.0

• preserve async_hooks context in client-side middlewares 31c0109

If there was an async_hooks context set in the first ('before' or 'after') middleware of both server and client then it will be preserved for all the other middlewares.

v2.3.0...v2.4.0

v2.3.0

• The server middlewares and the procedure is being called within same stack trace now. This allows setting the async_hooks context in a before middleware and it would propagate through the procedure and the after middlewares.
• The call context is not a transport responsibility any more. The new default argument _ will keep it from now on. The only predefined value there is procedureName. I.e. "_": { "procedureName": "myProc" }.
• The Lambda transport is now sending both old callContext+callArg and the new _ keys. But in the next breaking version of Allserver the callContext+callArg will go away.

v2.2.1...v2.3.0

v2.2.1

• Unit test for the new error messages 9068a5e
• Embed cause error text into message of unsuccessful calls a27effd

v2.2.0...v2.2.1

v2.2.0

Add support for AWS Lambda transport (invoking via the AWS SDK or even AWS CLI).

• Merge pull request #5 from flash-oss/add-support-for-direct-lambda-invocation 0871c42
• Add missing headers to the HTTP lambda context 5112cc9

v2.2.0-1...v2.2.0

v2.2.0-0

• Add support for direct AWS Lambda invocation b22c14f

v2.1.0...v2.2.0-0

v2.1.0

In memory

Sometimes you need to unit test your procedures via the AllserverClient. For that we have MemoryTransport.

const { Allserver, MemoryTransport } = require("allserver");

const memoryServer = Allserver({
    procedures,
    transport: MemoryTransport(),
});

const client = memoryServer.start();

const { success, code, message, user } = await client.updateUser({
    id: "123412341234123412341234",
    firstName: "Fred",
    lastName: "Flinstone",
});

assert(success === true);

• improve README b72d58a
• Add new transport - in Memory 0209924

v2.0.1...v2.1.0

v2.0.1

• Logging arguments rearrange a559992

v2.0.0...v2.0.1

v2.0.0

peerDependencies

When allserver reached v1.0.0 stability the "optional peerDependencies" feature was not yet generally available. But 2 years later the npm v7 is more widespread. So this release introduces "optional peerDependencies" with this commit: 58e86db

From now on every runtime (production) dependency version can be found in the peerDependencies of our package.json.

In addition, we're taking chance of updating these peer deps whilst increasing SemVer MAJOR from v1 to v2. Hence, micro@10 is required instead of v9. BullMQ better be latest version bullmq@3.10 (has fewer bugs). Also, the HttpClientTransport.js will try using built-in fetch instead of node-fetch.

Commit log

• Upgrade peerDep modules for GRPC, BullMQ, HTTP protocols 3d10cf7
• Try fixing tests in over Node versions 67f4a0c
• Try fixing tests in over OSes ce094f2
• Speedup unit tests. Ensure it works with the Node built-in fetch 1c72970
• Use npm v7 feature "optional peerDependencies" for all production dependencies 58e86db
• Upgrade micro dependency to v10 27777cb

v1.3.0...v2.0.0

v1.3.0

• Add support for Express.js as the server side transport. c79787a

v1.2.0...v1.3.0