BUGFIX: Prevent unexpected token errors with various loaders

[Sebobo]

When I try to include the library in a web pack build I get the following error due to the optional chaining character:

Module parse failed: Unexpected token (666:21)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|                               for (let ti = 0; ti < terms2.length; ti++) {
|                                       // no haystack item contained all terms
>                                       if (preFiltered?.length == 0)

[Sebobo]

Hm I see now that the library is compiled to ES2020 standards which includes the operator.
I have to target some older version, therefore I need to find a different way to build this.

[leeoniya]

specifically, it's Webpack 4 :(

Webpack 5 (released in 2020) and all modern tools and browsers should have no problem.

https://caniuse.com/mdn-javascript_operators_optional_chaining

[Sebobo]

Yes sadly I can't update the web pack version as it's a plugin for a framework that provides the web pack config but I created a patch for now with yarn in my app to adjust the ?? ?. operators and got it working this way.