Most "enterprise" application backends are still written in Java (and probably C#) combined with a frontend based on Angular, sometimes Reacts or older technologies. I am not aware of any Node-based backend at any of our customers (medium/large German companies), except maybe for some smaller parts of the backend (microservices architecure etc.)
Ah, also, not sure if you were joking, but I don't think using JavaScript (TypeScript, that is) in both frontend and backend is a bad idea. Having a shared (domain) model can be a real boon. Admittedly, JavaScript lacks a few things that is offered by Java and the like that makes not yet fit for larger applications though (say DI, modularization and so on).
For what it's worth, I can confirm that a lot of backend developers look down to frontend developers, but if you dig a little deeper you often (not always) see that frontend development is simply intimidating to them and they rather stick to what they know. At least in my country/region this leads to a lack of good frontend developers; good developers being those that apply well-known and established (backend) practices to the frontend.
Save navigation and equals/hashCode (as protocol, not using that ValueType thingy) are fine and definitely useful, but otherwise we should avoid adding even more syntax elements to JS.
- Actions can fail, but still continue (more like an additional success/failure status)
- Manually triggered actions (maybe with parameters that need to be entered by the user)
- Artifacts attached to actions especially HTML reports (next to plain text, this is the universal output type for a lot of quality tools)