The scripting library completely abstracts away the details of the underlying JS runtime. Clients depending on the scripting library do not themselves depend on the library implementing the JS runtime, currently MozJS. However, during a dynamic link, the library dependency graph expansion causes the JS runtime library to be spammed onto the link line for all targets that link the scripting library, even though none of them need to see it. Only the scripting library needs to list the JS runtime on its link line.

We have newly added a mechanism to express this situation in SERVER-27505; use it here to ensure that the large JS runtime library is only placed on the link line when truly required.