nact ⇒ node.js + actors ⇒ your services have never been so µ

Last update: Dec 28, 2022

Overview

nact ⇒ node.js + actors
your services have never been so µ

Any and all feedback, comments and suggestions are welcome. Please open an issue if you find anything unclear or misleading in the documentation.

This is the repository for the javascript implementation. To view/contribute to the ReasonML code, go to http://github.com/ncthbrt/reason-nact. To contribute to the documentation, https://github.com/ncthbrt/nact.io is the place to make PRs.

Nact is redux but for the server

Servers today are very different from those even 10 years ago. So why are we still programming like it's the 90s?

Inspired by the approaches taken by Akka and Erlang, Nact is an open source Node.js framework which enables you to take control of your state to:

more effectively use memory
improve application resiliance
increase performance
reduce coupling

With out of the box support for event sourcing, and a considered implementation of the actor model, nact can work across a wide variety of domains.

Nact is no silver bullet, but it is evolving to tackle ever more demanding use cases. Perhaps one of them is yours?

To get started, head to https://nact.io

Note: Nact is currently only able to work on Node 8 and above.

The Next Branch

You might have noticed that the default branch has been changed to next. That is because Nact is undergoing a signficant rearchitecture.

The aim is to make modularity and extensibility a first class citizen of Nact, while still going to great pains as always to ensure a seamless upgrade path. This work will enable Nact to run in more contexts, such as the browser, deno and of course nact's original platform node. It will also allow for some exciting work in enabling location transparency and being able to more easily design and operate distributed architectures, especially in k8s and cloud contexts.

Of course due to the churn, and because the Nact API surface is expanding, it also seemed prudent to port the codebase over to typescript.

The changes will also require a rewrite of the documentation.

A note on regularity of commits

Nact sees daily usage by the project maintainer. The project is extremely stable and has been around for a few years. As the project made the deliberate choice to minimise dependencies, particularly runtime dependencies, there is not a huge need for updates to the project, besides for the occasional introduction of new features. This means that it can be a few months since the last commit. This does not mean the project is dead, but rather that it is working as designed.

How are you using Nact?

We would love to hear how you're using Nact. If you'd like to send feedback (bad or good) please email Natalie Cuthbert at [email protected] or join the Discord.

License

Comments

Typescript ActorRefs are unsoundly typed.
I've started a branch /refactor-typescript to address these issues.

Problems present on current dev branch are as follows:

Sender - The sender property makes sound typing impossible as it either couples the senders and recipients too tightly together or it removes the type information. Sender is to be removed in a soundly typed implemention. c.f. reason-nact

Children - The Children Ref of a given actor are currently typed ActorRef<any> they should be instead changed to ActorRef<unknown> to indicate that by default we do not know what messages a child can handle in advance. In general any any should be removed from the public facing api.

Context, SupervisionContext, Actor all need to include the message type of the parent as well as the current actor. This IS known by a child actor in advance and allows a child actor to freely message a parent without casting.

Serialized messages and decoders/encoders - Messages coming back from the database cannot be soundly typed as this is out of nact's control. Persistent actors should be typed as Json by default unless they include a encoder/decoder tuple which maps Json to an actual type.

Unrelated to soundness, but still important:

References - Currently references include get methods and extraneous fields. These fields and methods need to be removed as references must be serializable to json without information loss.

Separation of implementation details from public API - Nact is kind of like an iceburg. There is a lot of implementation details that users don't need to directly interact with unless they wish to extend the framework. It would be nice to make it clearer in source which files are part of the public API and which are not. Currently I removed implementation details to a folder called internals (for want of a better name)

typescript
opened by ncthbrt 15
Nact in browser
It'd be an interesting development to get nact working in the browser. There is no fundamental reason right now why it wouldn't be possible. This would enable a few things:

It could take the place of redux.

Allow very clean client-server communication via websockets/http2/etc

feature
opened by ncthbrt 15
First draft of Logging feature implementation
Fixes #21

Description

Added module 'nact/monitoring' with configureLogging as the most important functionality. It is an extension for ActorSystem that includes a loggingEngine in the system and provides of a property log to the context of each message processing.

Related Issue

This PR gives solution to issue #21.

Motivation and Context

I would like to participate in the development of this project and took a simple 'up for grabs' issue to start familiarizing with the code.

How Has This Been Tested?

This feature was tested with unit testing using mocha, chai and sinon.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have read the CONTRIBUTING document.

[x] I have added tests to cover my changes.

[x] All new and existing tests passed.
opened by iskandersierra 13
Suggestion - use generator yield for dispatching messages
This framework looks extremely interesting.

I was wondering, have you considered following a "redux-saga" like model for dispatching messages between actors? e.g.:

const pingBehavior = async (msg, ctx) => { console.log(msg); await delay(500); yield dispatch(ctx.sender, ctx.name, ctx.self); // <--- here's where this differs from the docs example. }; const ping = spawnStateless(system, pingBehavior, 'ping');

Where dispatch() would just produce an object which is used by the framework to do the actual sending:

const dispatch = (actor, msg, sender) => ({ DISPATCH: { actor, msg, sender }});

This would make actor "behaviour" functions potentially side-effect free, which would have testability benefits.
opened by samfrances 12
Snapshotting has one-state lag, leading to "Failed to take snapshot Error: data should not be null or undefined"
Expected Behavior

The snapshot is taken on the state after the first message, rather than on the null state.

Current Behavior

With snapshotEvery: 1 * messages, I noticed that the snapshot is always one state behind.

This also leads to the error "Failed to take snapshot Error: data should not be null or undefined" when nact tries to persists the first time.

Steps to Reproduce (for bugs)

Spawn a persistant actor with the option {snapshotEvery: 1 * messages}

Process a message to create the state object

Context

It'd be nice if the snapshot took place after the message is processed rather than before (if that's indeed what's happening). This would ensure that the snapshot is really up-to-date and avoid re-processing the last message every time the actor is restarted.

Your Environment

Version used: 6.1.0 (and nact-persistence-postgres v6.0.2)

Environment name and version (e.g. Node v8.8): node 9.6

Operating System and version: OS X 10.10.5
opened by ellis 10
Rewrite in TypeScript
Expected Behavior

Type definitions for TypeScript (index.d.ts) should be provided.

Current Behavior

There is no type definition provided, either in nact or @types/nact.

Possible Solution

https://github.com/civilizeddev/nact/blob/master/lib/index.d.ts I wrote this above, using it in my own project. I just want to share it.

if you contributors are pleased I think it would be better to rewrite the whole project in TypeScript.

Context

I am also Java and Scala developer, but currently working with TypeScript in Node. I was pleased that there is akka-like actor implementation even in JavaScript. Thank you.

Your Environment

nact 7.2.1

Node 8.15.0 LTS

TypeScript 3.3.3
opened by civilizeddev 8
Add optional 3rd argument sender to dispatch typing
Dispatch accepts a 3rd optional argument, but typing for dispatch does not reflect this. This PR updates this.

Description

Update dispatch typing to reflect its ability to accept a 3rd optional argument, sender.

Related Issue

https://github.com/ncthbrt/nact/issues/86

Motivation and Context

This allows for importing nact using import statements instead of require with typescript.

How Has This Been Tested?

Updated the changes here, and then ran repro steps in ticket and found issue to be resolved.

Screenshots (if appropriate):

Types of changes

[x ] Bug fix (non-breaking change which fixes an issue)

[ ] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x ] My code follows the code style of this project.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[x ] I have read the CONTRIBUTING document.

[ ] I have added tests to cover my changes.

[ ] All new and existing tests passed.
opened by Choongkyu 5
feat(actor): allow async initialStateFunc
Add the ability to supply an actor with an async initialStateFunc

Description

This change includes:

Changing the type of the initialStateFunc for Actor to include functions that return a Promise<State>

Add Actor#waitUntilInitialized to wait until the state has been initialized

Calling waitUntilInitialized as part of Actor#handleMessage to prevent processing messages until the initialize function is called

Add unit tests to test using async initialStateFunc both under normal circumstances and when throwing an error

Related Issue

Motivation and Context

This allows for Actors have state that is initialized asynchronously. This functional example that this was added to solve is having an actor that relies on some feature flag value that can only be retrieved using an asynchronous function.

How Has This Been Tested?

I have added unit tests to test that the dispatch works correctly when using an asynchronous initialStateFunc. Similarly, I've added a unit test to make sure that if an error is thrown in an asynchronous initialStateFunc it will call the onCrash handler correctly.

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[x] I have read the CONTRIBUTING document.

[x] I have added tests to cover my changes.

[x] All new and existing tests passed.
opened by AceFire6 3
setImmediate polyfill

setImmediate is used in Nact to implement non blocking macro task semantics as it is more performant for this use case than setTimeout (which in many implementations has a minimum duration). However this API is not available in most browsers. Polyfilling this API may allow Nact to work in browser
enhancement

opened by ncthbrt 3
Could it be that `spawnPersistent` never returns if passed the same name twice?
Expected Behavior

I guess I'd expect spawnPersistent to either throw an error or return the existing child with the same name, rather than just not return.

Current Behavior

I was having a problem with not being able to query an actor twice: the first query succeeded, but then further queries timed out. I ended up tracking the problem down to spawnPersistent not returning when the same name was passed to it a second time.

Steps to Reproduce (for bugs)

Setup the system and actors like in https://nact.io/lesson/javascript/hierarchy

Mistakenly pass a fixed name to the spawn function, e.g. instead of childActor = spawnUserContactService(ctx.self, userId) do something like childActor = spawnUserContactService(ctx.self, "userId")

The Hierarchy documentation uses spawn, but I used spawnPersistent - I'm guess that's probably not important in this context.

Your Environment

Version used: 7.0.1 (and nact-persistence-postgres v7.0.0)

Environment name and version: node 9.6

Operating System and version: OS X 10.10.5

repro-required
opened by ellis 3
Clustering

One of the major benefits of actor systems is location transparency; being able to communicate with remote actors in the same way as local actors is an important feature of this

This feature could be as basic as having some means to allow actors to communicate when IP addresses are explicitly provided, or it could also include scheduling (deciding where actors should be put) and clustering.

Another important question is how to ensure that this architecture is flexible enough to support different kinds of transports, while selecting some sane, easy to setup defaults.
feature

opened by ncthbrt 3
dual package publishing using nanobundle

Description

Dual package publish config to support both CJS/ESM, dropped UMD format.

Switch bundler from Rollup to nanobundle, which is esbuild wrapper.

opened by cometkim 1
Bump minimist from 1.2.5 to 1.2.7 in /@nact/core
Bumps minimist from 1.2.5 to 1.2.7.

Changelog

Sourced from minimist's changelog.

v1.2.7 - 2022-10-10

Commits

[meta] add auto-changelog 0ebf4eb

[actions] add reusable workflows e115b63

[eslint] add eslint; rules to enable later are warnings f58745b

[Dev Deps] switch from covert to nyc ab03356

[readme] rename and add badges 236f4a0

[meta] create FUNDING.yml; add funding in package.json 783a49b

[meta] use npmignore to autogenerate an npmignore file f81ece6

Only apps should have lockfiles 56cad44

[Dev Deps] update covert, tape; remove unnecessary tap 49c5f9f

[Tests] add aud in posttest 228ae93

[meta] add safe-publish-latest 01fc23f

[meta] update repo URLs 6b164c7

v1.2.6 - 2022-03-21

Commits

test from prototype pollution PR bc8ecee

isConstructorOrProto adapted from PR c2b9819

security notice for additional prototype pollution issue ef88b93

Commits

c590d75 v1.2.7

0ebf4eb [meta] add auto-changelog

e115b63 [actions] add reusable workflows

01fc23f [meta] add safe-publish-latest

f58745b [eslint] add eslint; rules to enable later are warnings

228ae93 [Tests] add aud in posttest

236f4a0 [readme] rename and add badges

ab03356 [Dev Deps] switch from covert to nyc

49c5f9f [Dev Deps] update covert, tape; remove unnecessary tap

783a49b [meta] create FUNDING.yml; add funding in package.json

Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for minimist since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump minimatch from 3.0.4 to 3.1.2
Bumps minimatch from 3.0.4 to 3.1.2.

Commits

699c459 3.1.2

2f2b5ff fix: trim pattern

25d7c0d 3.1.1

55dda29 fix: treat nocase:true as always having magic

5e1fb8d 3.1.0

f8145c5 Add 'allowWindowsEscape' option

570e8b1 add publishConfig for v3 publishes

5b7cd33 3.0.6

20b4b56 [fix] revert all breaking syntax changes

2ff0388 document, expose, and test 'partial:true' option

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump qs from 6.5.2 to 6.5.3 in /@nact/core
Bumps qs from 6.5.2 to 6.5.3.

Changelog

Sourced from qs's changelog.

6.5.3

[Fix] parse: ignore __proto__ keys (#428)

[Fix] utils.merge: avoid a crash with a null target and a truthy non-array source

[Fix] correctly parse nested arrays

[Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (#279)

[Fix] utils: merge: fix crash when source is a truthy primitive & no options are provided

[Fix] when parseArrays is false, properly handle keys ending in []

[Fix] fix for an impossible situation: when the formatter is called with a non-string value

[Fix] utils.merge: avoid a crash with a null target and an array source

[Refactor] utils: reduce observable [[Get]]s

[Refactor] use cached Array.isArray

[Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (#269)

[Refactor] parse: only need to reassign the var once

[Robustness] stringify: avoid relying on a global undefined (#427)

[readme] remove travis badge; add github actions/codecov badges; update URLs

[Docs] Clean up license text so it’s properly detected as BSD-3-Clause

[Docs] Clarify the need for "arrayLimit" option

[meta] fix README.md (#399)

[meta] add FUNDING.yml

[actions] backport actions from main

[Tests] always use String(x) over x.toString()

[Tests] remove nonexistent tape option

[Dev Deps] backport from main

Commits

298bfa5 v6.5.3

ed0f5dc [Fix] parse: ignore __proto__ keys (#428)

691e739 [Robustness] stringify: avoid relying on a global undefined (#427)

1072d57 [readme] remove travis badge; add github actions/codecov badges; update URLs

12ac1c4 [meta] fix README.md (#399)

0338716 [actions] backport actions from main

5639c20 Clean up license text so it’s properly detected as BSD-3-Clause

51b8a0b add FUNDING.yml

45f6759 [Fix] fix for an impossible situation: when the formatter is called with a no...

f814a7f [Dev Deps] backport from main

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump decode-uri-component from 0.2.0 to 0.2.2 in /@nact/core
Bumps decode-uri-component from 0.2.0 to 0.2.2.

Release notes

Sourced from decode-uri-component's releases.

v0.2.2

Prevent overwriting previously decoded tokens 980e0bf

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

v0.2.1

Switch to GitHub workflows 76abc93

Fix issue where decode throws - fixes #6 746ca5d

Update license (#1) 486d7e2

Tidelift tasks a650457

Meta tweaks 66e1c28

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

Commits

a0eea46 0.2.2

980e0bf Prevent overwriting previously decoded tokens

3c8a373 0.2.1

76abc93 Switch to GitHub workflows

746ca5d Fix issue where decode throws - fixes #6

486d7e2 Update license (#1)

a650457 Tidelift tasks

66e1c28 Meta tweaks

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump decode-uri-component from 0.2.0 to 0.2.2
Bumps decode-uri-component from 0.2.0 to 0.2.2.

Release notes

Sourced from decode-uri-component's releases.

v0.2.2

Prevent overwriting previously decoded tokens 980e0bf

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

v0.2.1

Switch to GitHub workflows 76abc93

Fix issue where decode throws - fixes #6 746ca5d

Update license (#1) 486d7e2

Tidelift tasks a650457

Meta tweaks 66e1c28

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

Commits

a0eea46 0.2.2

980e0bf Prevent overwriting previously decoded tokens

3c8a373 0.2.1

76abc93 Switch to GitHub workflows

746ca5d Fix issue where decode throws - fixes #6

486d7e2 Update license (#1)

a650457 Tidelift tasks

66e1c28 Meta tweaks

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0

Releases(v7.3.0)

v7.3.0(Jun 12, 2020)

Added the ability to read the mailbox in onCrash and afterStop event handlers.
Source code(tar.gz)
Source code(zip)
v7.1.0(May 18, 2018)
This new feature is especially for architectures which may require a CQRS approach.

A persistentQuery is similar to an actor, except it cannot cannot persist messages, does not have context and checks the event store each time it is invoked for messages it has not yet processed (later versions may may use of streaming). Additionally a persistent query supports snapshotting of state, making it ideal as an event model.

Usage is below, however a more detailed tutorial is to follow on nact.io once the reason version is published:

let query = persistentQuery( system, (result, msg) => apply(result,msg), 'persistenceKey', { cacheDuration: 10 *minutes, snapshotKey: 'test', snapshotEvery: 5 * messages } ); let result = await query();
Source code(tar.gz)
Source code(zip)
v7.0.0(May 10, 2018)
Changes

Former behaviour was for an stateful/persistent actor to shutdown if it the next state was a falsey value. This has been removed as it isn't hugely useful and is a little bit too implicit for my liking. Think it creates confusion more than anything else.

Adjusted snapshotting behavior to discretely snapshot. This means that snapshots only are scheduled after a message has been completely processed.

Removed some branching.

Removed some allocations

Added hooks for encoders and decoders for both persistent messages and snapshots. This will make the reason wrapper of nact a lot more efficient. (It's currently performing a json serialize/deserialize every message, a massive hack that was done as an emergency fix in a production scenario)

Source code(tar.gz)
Source code(zip)
v6.1.0(Apr 16, 2018)

Source code(tar.gz)
Source code(zip)
v6.0.1(Apr 11, 2018)

Fixes issue #42
Source code(tar.gz)
Source code(zip)
v6.0.0(Apr 4, 2018)

Please note that the Postgres Persistence engine is also required to be upgraded with this breaking change.

The only user facing change is that the state$ operator has been removed as was previously announced.
Source code(tar.gz)
Source code(zip)
v5.0.0(Mar 6, 2018)

Specifying a supervision policy has now been moved to the child rather than the parent. This is to allow ReasonNact to correctly type the policy and include the message which resulted in the fault. Please see https://nact.io/lesson/javascript/supervision for changes to usage.
Source code(tar.gz)
Source code(zip)
v4.4.4(Jan 23, 2018)

Source code(tar.gz)
Source code(zip)
v4.4.3(Jan 21, 2018)

Source code(tar.gz)
Source code(zip)
v4.4.2(Jan 17, 2018)

Source code(tar.gz)
Source code(zip)
v4.4.1(Jan 17, 2018)

Source code(tar.gz)
Source code(zip)
v4.4.0(Jan 16, 2018)

Source code(tar.gz)
Source code(zip)
v4.3.0(Dec 20, 2017)

Instructions can be found at: https://nact.io/lesson/javascript/supervision
Source code(tar.gz)
Source code(zip)
v4.2.0(Dec 9, 2017)

Source code(tar.gz)
Source code(zip)
v4.1.0(Dec 5, 2017)

The query function can now optionally accept a message function. This function takes in the temporary actor reference and returns the message to dispatch to the sender. This is to cater for the use case where actors expect an actor reference in a message.
Source code(tar.gz)
Source code(zip)
v4.0.1(Dec 4, 2017)

Source code(tar.gz)
Source code(zip)
v4.0.0(Dec 3, 2017)

Source code(tar.gz)
Source code(zip)
v3.2.0(Dec 2, 2017)

Source code(tar.gz)
Source code(zip)
v3.1.5(Nov 20, 2017)

Y not /shrug
Source code(tar.gz)
Source code(zip)
v3.1.4(Nov 4, 2017)

This release does not break userland.
Source code(tar.gz)
Source code(zip)
v3.1.3(Oct 31, 2017)

The type check forced the PostgreSQL plugin to update in lockstep with nact, which is not desirable.
Source code(tar.gz)
Source code(zip)
v3.1.2(Oct 30, 2017)

Source code(tar.gz)
Source code(zip)
v3.1.1(Oct 30, 2017)

Fixed #15: query now throws an error if no timeout is provided. This prevents the system becoming unresponsive.
Source code(tar.gz)
Source code(zip)
v3.1.0(Oct 28, 2017)

While strictly speaking a breaking change, I'm not bumping the version number as this comes hours after version 3's breaking change which touches code in the same ways.

I decided to make the query, dispatch and stop methods functions in the public interface. This will make it significantly simpler to later pass remote actor references as JSON.
Source code(tar.gz)
Source code(zip)
v3.0.0(Oct 28, 2017)
Dispatch has been removed from the context object. While handy, it was actually that much less verbose and meant that users need to learn two ways of dispatching messages. Fix for Issue #14

Stateless actors are now concurrent. This means they can process more than one message at a time. This allows a performance increase without a resultant increase in complexity. Enhancement #13

Source code(tar.gz)
Source code(zip)
v2.1.0(Oct 23, 2017)

Actors references now have a state$ object which returns an observable which emits a value each time the state of the actor changes.
Source code(tar.gz)
Source code(zip)
v2.0.3(Oct 23, 2017)

Removed undocumented ability to retrieve children from outside the actor
Source code(tar.gz)
Source code(zip)
v2.0.2(Oct 18, 2017)

Source code(tar.gz)
Source code(zip)
v2.0.0(Oct 9, 2017)

Source code(tar.gz)
Source code(zip)