This should help improve the autocrlf issue in Windows.

Without libjs in tree, this can't realistically be built.  Our legacy
is stored in the version control history.

we have already removed the module from tree, no need to bootstrap/configure the lib still, or to have it in tree at all for that matter

* commit 'e3b0d721':
  Fix BLF confusion when dealing with the same extension in multiple domains