Commits to master since this release
To install the developer build:
- Firefox: Click uBlock0_1.37.3b8.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.3b8.thunderbird.xpi, then drag-n-drop it into Thunderbird's Add-ons Manager pane (Thunderbird 78+ required)
- NodeJS: Download and unzip uBlock0_1.37.3b8.nodejs.xpi.
New
A new NodeJS package will now published with every release. The package allows to import and use uBO's static and dynamic filtering engines 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 engines in a NodeJS package. The ability to run code from a NodeJS package also opens the door to have test coverage in uBO.
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.
Since I have little experience with dealing with NodeJS environment/packages, thanks to @mjethani for assistance.
Closed as fixed:
- [patch by @vtriolet] TypeError in noscript-spoof scriptlet with invalid meta refresh URL
- TypeError when trying to use element picker on plaintext resource
- 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 supported browsers has been increased to Chromium 61, Firefox 60, and Opera 48.
- 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
- Refactor hntrie to avoid the need for boundary cells
- Fix bad test in WASM version of HNTrieContainer
- Export the rule-based filtering engines to the nodejs package
- Rewrite logical expressions for ESLint
- [patch by @mjethani] Add Makefile
- [patch by @mjethani] Make uAssets a submodule
- Ensure compiled sections are ordered in ascending id
- Fix handling of some procedural cosmetic filters with explicit
:scope