What is the status of this library?

[antonkatz]

Is it stable? Are there plans to continue maintaining it?

Thanks

[tvcutsem]

Speaking as the original author of this library: the core API of traits.js has been unchanged for many years now, so it can be considered very stable. traits.js is a very small library: there are only a handful of API calls, and together they pretty much cover all that is needed to do trait composition in JS. In recent years @dotnetCarpenter has been maintaining the library as a proper NPM module, but I have no view on his future commitments.

This library has few maintainers, so that's something to be aware of. On the other hand, the library is small, tested, stable and simple, which helps to keep bugs to a minimum.

[dotnetCarpenter]

@antonkatz Hello there. In my opinion traits.js is feature complete. I have used it in a few commercial projects and aside from things that could be improved when used with class, there are no known bugs or issues.

I have very little time to dedicate to this project and the two issues that has been reported has unfortunately slipped "under my radar". They both look like questions, rather than bugs in the library.

The ES3 polyfill code is currently untested in CI because there is no readily available ES3 runtime to run the test suite in but all other code paths are covered.

I have intentionally not changed much since I believe it's a good sign that, as @tvcutsem says, "it can be considered very stable".
I did at one point create an example: https://github.com/traitsjs/traits.js/blob/master/examples/how-to-node-example.mjs to companion @tvcutsem's https://howtonode.org/traitsjs article.