Remove outdated note in "Interacting with code" docs (#26638)

`DEFAULT_LIBRARY_FUNCS_TO_INCLUDE` is not needed when
`EXPORTED_FUNCTIONS` is used

Fixes: #26629

Author: jhcarl0814

AUTHORS

@@ -602,3 +602,4 @@ a license to everyone to use it as detailed in LICENSE.)
 * Christian Lloyd <clloyd@teladochealth.com> (copyright owned by Teladoc Health, Inc.)
 * Sean Morris <sean@seanmorr.is>
 * Mitchell Wills <mwills@google.com> (copyright owned by Google, Inc.)
+* Han Jiang <jhcarl0814@gmail.com>

site/source/docs/porting/connecting_cpp_and_javascript/Interacting-with-code.rst

@@ -146,11 +146,6 @@ parameters to pass to the function:
        including function names.
        Exporting functions allows you to continue to access them using the
        original name through the global ``Module`` object.
-     - If you want to export a JS library function (something from a
-       ``src/library*.js`` file, for example), then in addition to
-       ``EXPORTED_FUNCTIONS``, you need to add it to ``DEFAULT_LIBRARY_FUNCS_TO_INCLUDE``,
-       as the latter will force the method to actually be included in
-       the build.
 
    - The compiler will remove code it does not see is used, to improve code
      size. If you use ``ccall`` in a place it sees, like code in a ``--pre-js``