At startup ./scripts/setup.sh there is such an error, how to fix it?

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }

https://github.com/naptha ?

If chosen from the local filesystem filenames with spaces do not work. This is probably not an issue for our integration as all filenames are changed first...but in the context of opening an archive (for example a Macos Application bundle) we see a failure when a path contains spaces (for instance "App Store"). This needs to be resolved or fixed

How to convert .txt to image?

It would cool to be able to support old ANSI colors and things like ASCII box drawing characters as well

For example if I google for "spacex pdf" then open in SecureView/p2. I get images that are ~4 Mb in size.

I could easily get the same quality if I used jpeg or compressed or resized these.

Yay

for instance a pages document is basically a zip file. so we unarchive it.

but what we should do is view it. We need a list of these types...or rather we need to check anything that presents as an archive against our existing extensions and run them through convert rather than explore

I noticed when running on mac that convert CPU util never hits above 100% even across multiple cores. Is there a way i can tune this at the command line? Or is it simply an OS level thing, so i need to renice for greater utilization?

Anyway, would be nice to be able to tune that, both up and down for different scenarios

Perhaps renice is the ultimate solution

some options are fragment link to page number, and fragment Link to text

I don't think we use ghostscript much but we should mitigate this

https://www.bleepingcomputer.com/news/security/critical-rce-found-in-popular-ghostscript-open-source-pdf-library/

I think a good way to conserve resources for potentially large jobs (large PDFs, 1000s of pages, displaying binary files, etc). Is to limit the output to the first 100 pages. And then put a link in the top that says (decode more). Which just runs the command again, but this time selects any remaining pages (if indeed this is possible!!). There are multiple ways to do this (limit to first mb of binary file) that may need to be different for different types.

Can debug and disassemble page by page to save resources and just send 1 page at a time. This is optimal for large binary files. And combined with a "preview mode" first 10 or 100 pages or whatever, it's an effective way to make it more efficient by limiting / capping total resource usage caused by a conversion.

Would be good to be able to set this

Somehow using the soffice command?

Perhaps a macro?

And also to expand to optimal width, with a maximum width after which all content wraps.

It's kind of weird right now. Surely there's a better way to convert them to images?

Demonstrate that the page is loading, otherwise it can be confusing when loading is slow..."Is the next page the same as the last? or...is the next page still just loading... ?"

it is used in convert.sh