Hi Ans,
Sorry for the confusion and I totally understand where you are coming from but history is against us here.
The confusing part is that we have paraviewweb a repository that contains old React widgets with the original infrastructure to talk back to a VTK/ParaView server which also contains many useful guide on VTK/ParaView Web (framework).
Nowadays, the client side (JS) is managed solely between vtk.js and wslink without the need of the paraviewweb repository/npm package.
And then we have the VTK/ParaView Web framework on which trame is based on. That is more a “marketing” name which is indeed built into VTK and ParaView on their Python side.
Finally the paraviewweb repository is technically in maintenance mode with no real update. And therefore contains some old and deprecated information.
ParaView-lite is indeed a ParaView-Web based application.
Nowadays, I will go to trame for any VTK/ParaView Web kind of solution. But then, if you want to develop your own web front end using Angular, React or else, I will still use trame on the server side and leverage vtk.js + wslink to talk to it.
I hope that clarify things a little better,
And thanks for asking such important question,
Seb