uBlock/platform/common
Raymond Hill 22022f636f
Modularize codebase with export/import
Related issue:
- https://github.com/uBlockOrigin/uBlock-issues/issues/1664

The changes are enough to fulfill the related issue.

A new platform has been added in order to allow for building
a NodeJS package. From the root of the project:

    ./tools/make-nodejs

This will create new uBlock0.nodejs directory in the
./dist/build directory, which is a valid NodeJS package.

From the root of the package, you can try:

    node test

This will instantiate a static network filtering engine,
populated by easylist and easyprivacy, which can be used
to match network requests by filling the appropriate
filtering context object.

The test.js file contains code which is typical example
of usage of the package.

Limitations: the NodeJS package can't execute the WASM
versions of the code since the WASM module requires the
use of fetch(), which is not available in NodeJS.

This is a first pass at modularizing the codebase, and
while at it a number of opportunistic small rewrites
have also been made.

This commit requires the minimum supported version for
Chromium and Firefox be raised to 61 and 60 respectively.
2021-07-27 17:26:04 -04:00
..
managed_storage.json Reorganize platform directory to avoid Chromium-centric appearance 2021-07-16 10:06:58 -04:00
vapi-background.js Modularize codebase with export/import 2021-07-27 17:26:04 -04:00
vapi-client-extra.js Reorganize platform directory to avoid Chromium-centric appearance 2021-07-16 10:06:58 -04:00
vapi-client.js Reorganize platform directory to avoid Chromium-centric appearance 2021-07-16 10:06:58 -04:00
vapi-common.js Modularize codebase with export/import 2021-07-27 17:26:04 -04:00
vapi.js Reorganize platform directory to avoid Chromium-centric appearance 2021-07-16 10:06:58 -04:00