Status of CSJS?

[tizmagik]

Hello @rtsao I just wanted to check in and see what the general plan and direction for CSJS is. We've noticed that it's been some time since the last release and there hasn't been any major new additions or developments into CSJS itself for some time.

Asking mainly from the perspective of react-csjs, one of the options we've have been looking into is shipping CSJS internally along with that package to make things like automatically including extended styles a bit easier (since we can wrap the CSJS instance in a singleton and control that interface for the user) just to name an example. There's a handful of other things we're thinking about for the future of react-csjs that this combination would enable.

@wKovacs64 @drcmda and I would like to get your thoughts and see if you think this makes sense, etc.

[rtsao]

I've been busy with other things lately so admittedly CSJS has been neglected a bit. Since the scoping configuration stuff is going to be a breaking change, I've delayed release until I can roll in some other changes.

I've just recently been doing some general cleanup and refactoring here: https://github.com/rtsao/csjs/tree/dev

For v2.0 I'm looking at:

• Cleanup/refactor codebase to make it easier to understand and ensure concerns/abstractions are in the right place so the business logic of CSJS is more composable.
  • This includes making configuration of scoping better (including disabling it altogether)
• Added support for single class mode #25
• Improve package setup/tooling (ES6 codebase, rolled-up bundles for smaller size, etc.)

I had originally wanted to work on performance but it ended up being pretty challenging (and require a tooling-heavy solution, which is ultimately sort of anathema to the original idea) which was a bit discouraging. So I think working on more straightforward goals like the above that improves UX and DevExp is a better strategy (at least in the near term).

I'm really glad you've made react-csjs since it's a true out-of-the-box working CSJS solution. One of the goals I had for this project was to be very minimal and completely framework agnostic (so to allow things to be built on top), but as a result it takes a bit of effort to use straight away.