winutils VS pkg

Create a folder still in the root folder of your C: drive named Hadoop. Then, click this repository link, identify the bin folder of your Spark installation Hadoop version, and download the winutils.exe file.

Contain links to outdated winutils builds. There should be newer builds here.

Using JavaScript as an example again, what if the build output is a single binary file? Was it scripted, or was it programmed? It's not a theoretical question, because there are tools that do exactly this: https://github.com/vercel/pkg

https://github.com/vercel/pkg .

You write a server in Node.js, compile it to an exe with Vercel Pkg and users run the exe on their local machine and use it with their browser.

Instead of running an app "in the cloud" they run it on the server on their machine. But the server could easily also be moved to the cloud as well.

Using a browser to connect to an app running on your local machine has the nice feature that you can open any number of browser-views on it, looking at the app and your data and tools from multiple viewpoints. Since it is local they are the only user and don't need to login or "keep a session" and can thus interact with the app in multiple ways in parallel.

I don't need to design in a feature that allows users to "open a new window". That is handled by the browser. Open a new tab to the same or different (bookmarked) url.

The two best libraries are pkg and caxa.

I figured out how to do it using vercel/pkg - its amazing!

https://github.com/vercel/pkg is one example

I've personally used `nexe` before and ended up swapping it out for Vercel's `pkg`[1]. `pkg` worked better with building ARM binaries and with less gotchas with multiplatform builds, in my experience.

[1]: https://github.com/vercel/pkg

Take a look on this project https://github.com/vercel/pkg

For the packaging we will use the pkg library. But unfortunately pkg is not supporting ES modules which we configured by adding the "type": "module" to the package.json. So before we can use pkg we need to compile our script to a version which is not using ES modules. To do the compilation we will use esbuild. esbuild can also bundle our script into one file, so no dependencies on a node_modules folder are left in the compiled file. So let's install it.