davidhq

Here it is also true that only one request with a big `limit` and default zero `offset` can be used and nothing else, right? Cannot rely on FlexSearch pagination if...

This means that one has to use bigger `limit` to do it right? And kind of never use the `offset` option.

> This could be anecdotal, but it seems like this issue is possibly surfacing whenever Brave has updated but needs to be relaunched. Interesting ... > Is there any data...

@BrendanEich .elevatePriority() @luke3butler wrote ↴ > Could elevated priority for this issue be considered? I have some clients that use Brave company-wide and are ready to test alternatives because of...

I still plan to do this :) It might move to early next year.

+1

@ts-thomas would replacing `google-closure-compiler` with something else potentially solve the problem? If you think yes, I can look into how to do it... I had some other problem with `google-closure-compiler`...

* and webpack as well... maybe some more modern tool can replace both `webpack` and `google-closure-compiler` ... also is Babel needed at all? It is also obsolete, I believe

I did more exploring... so that part of documentation mentioned above is indeed wrong... there is similar passage in **Tags** section: > This gives you result which are tagged with...

> * pnpm improves the development experience (saves a lot of disc space) Have you tested this ? I actually have and it never saved any disk space. pnpm works...