Commits to master since this release
To install the developer build:
- Firefox: Click uBlock0_1.37.3b2.firefox.signed.xpi.
- Chromium: Install from the Chrome Web Store (CWS): https://chrome.google.com/webstore/detail/ublock-origin-dev-build/cgbcahbpdhpcegmbfconppldiemgcoii.
- Thunderbird: Download uBlock0_1.37.3b2.thunderbird.xpi, then drag-n-drop it into Thunderbird's Add-ons Manager pane (Thunderbird 78+ required)
- NodeJS: Download and unzip uBlock0_1.37.3b2.nodejs.xpi.
New
A new NodeJS package will now published with every release. The package allows to import and use uBO's static network filtering engine into NodeJS. This is currently minimal and a first iteration, and issues regarding the NodeJS package are accepted in order to improve usability of uBO's filtering engine as as a NodeJS package.
For now the package can be downloaded and unzipped locally. Once installed, you can execute node test in the root of the package to verify that the static network filtering engine works properly. For usage, refer to the test.js, or ublock.js used in Cliqz's benchmark.
A current limitation is that the WASM code paths can't be enabled since currently the WASM modules are loaded using the Fixed in 1.37.3b2.
fetch() API, which is not available as default API in NodeJS. I will attempt to identify a solution in a future version.
Since I have little experience with dealing with NodeJS environment/packages, thanks to @mjethani for assistance.
Closed as fixed:
- Split out core functionality into separate module
- This is of course an ongoing work for the foreseeable future, but the concrete goal sought in the issue has been reached, i.e. the static network filtering engine can be used as a nodejs module with no external dependencies.
- Since uBO's codebase now uses JS modules, the minimum version of some browsers has been increased to Chromium 61 and Opera 48. For Firefox 59 or less, you will have to toggle the
thedom.moduleScripts.enabledpreference totrue.
- This is of course an ongoing work for the foreseeable future, but the concrete goal sought in the issue has been reached, i.e. the static network filtering engine can be used as a nodejs module with no external dependencies.
Notable commits without en entry in the issue tracker
- Ensure compiled sections are ordered in ascending id
- A regression in 1.37.1b1 as a result of this commit was fixed in 1.37.1b2, and you may need to force an update of filter lists which were updated in 1.37.1b1.
- A regression in 1.37.1b1 as a result of this commit was fixed in 1.37.1b2, and you may need to force an update of filter lists which were updated in 1.37.1b1.
- Fix handling of some procedural cosmetic filters with explicit
:scope