I might be missing the problem here. You can create ArticlePage with needed functionality in the extension or mediawiki/core (if you need the same functionality in several extensions).
Topic on User talk:Jdlrobson/Experiences porting Ruby browser tests to NodeJs
Sure, but nothing exists (yet) in mediawiki/core. This means we are starting with a blank slate. To be honest, I am a little frustrated that we have shifted from Ruby to Node without providing the infrastructure need to make that shift.
We need to switch from Ruby to Node because Ruby is no longer supported. What is implied by this is that we need to rebuild the entire Ruby support libraries that we have been using and that we are responsible for doing that.
This is a lot of work (and I'm personally finding it overwhelming and stressful). We are a small team with lots of key products and are struggling to find the time to fit this work in alongside all the other work we need to do. Progress is slow.
I understand the frustration. We are also a small team and I am the only one working on Selenium support. Please understand that I could not really know what features other teams would need. I did my best. The best way to resolve this would be to pair on implementing the required features. Another way would be to create tickets in Phabricator and assign them to me.