I had a quick look and.. I have no idea. Frontend development at meta works differently than you probably imagine: things aren’t built locally but on dev servers or on-demand instances that all run services that take care of any build jobs in the background. I don’t know if there’s any nodejs involved at any point there or later in CI, but I suppose it’s possible. I still think it’s unlikely because my search turned up barely any mentions of nodejs, so I still think that my main point holds true: there’s very little node in use at meta, and nearly all the facebook frontend services are php (or python for Instagram/threads)
I've didn't think "no more PHP". I am just seeing how much non-PHP Meta open sources and talk with Meta guys at events who are building stuff for JS, talking about new client and varied tech stack and then you've told me "actually its still mostly PHP".
That’ll be because Facebook doesn’t use PHP as such, but Hack, which isn’t compatible with vanilla PHP. Hack isn’t really used much outside of Meta, so what’s the point of going through the extra work of open sourcing our stuff if nobody else will ever use it?
