Who wants to take part in the development of a JS framework based on the Yii Framework v2 architecture?

Question

JavaScript

Good day! If you are a php / js programmer who likes the Yii Framework and wants to develop somewhere further, then my proposal will probably be of interest to you.
Foreword
About a year ago I happened to change the architecture of a large legacy php project that had problems with loads and architecture. It was decided to rewrite its loaded parts on nodejs. Since I am a fan of the yii framework, when creating the bike, I took many ideas from yii.
Then the idea came up to make a port of the Yii framework to javascript.
PHP framework -> JavaScript?
Of course, quite a few problems pop up in this approach: language asynchrony, browser limitations, application life cycle, etc. But as it turned out, all problems are completely solvable.
Moreover, I set myself to make a framework that works both on node js and in the browser.
What is now?
A lot of work has already been done. You can see it on github. The basic functionality of the Yii framework has already been done in the first cast and is used in the above project. Here's what's already there:
- Basic entities: Object, Component, Module, Application, Model, ..
- Models supporting schemas, validators, errors
- Basic validators: boolean, compare, date, default, double, email, filter, in ( range), integer, match, number, required, safe, string, url
- Active Record for Redis
- Controllers and
actions - UrlManager (router parsing, 1 in 1 supporting Yii2 syntax)
- Yii::$aliases
- Rendering templates and layouts (template engine - underscore)
All this works both in the browser and in chrome. The entire API and structure is as close as possible (if possible) to Yii2. Tests for models, validators, aliases, and route parsing are also written.
You can see code examples in the tests and sample application.
What else do you need and why do you need a community?
Yii is very large, so you can adopt a lot more from there - my hands are not enough. First of all, these are:
- Bulder queries and Active Record for SQL
- Widgets
- REST API
- Mail
- Various helpers
- etc.
And you always need an objective view of the architectural decisions made.
What advantages are/will be over Meteor/Derby/..?
- Low threshold of entry. At least for those who are familiar with yii
- Inherited from Yii: simplicity, extensibility, ..
- Ability to use any other libraries (now Jii uses lodash, jquery, express, ..).
PS: I would love to hear your opinions/ideas/suggestions!

Answer 1

What's good about YII?

Answer 2

Clean up the repository. node_modules and .idea need to be added to .gitignore
Some kind of README on github is also needed.

Answer 3

Offtopic. Why does this question have answers marked as "an hour ago"? Although I remember exactly that this question and these answers were a long time ago

Answer 4

This has been around for a long time: developer.uz/blog/restful-api-in-yii2
This is a description of REST for yii2. And then use any js framework and send requests to yii and get json in response