Does pkg supersede enclose? There appears to be a relationship between the two project

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

What is the relationship of pkg to enclose? about pkg HOT 6 CLOSED

zeit commented on July 19, 2024 11

What is the relationship of pkg to enclose?

from pkg.

pmq20 commented on July 19, 2024 12

😄 Also checkout node-compiler with differences being,

Project	Differences
pkg	Pkg hacked `fs.*` API's dynamically in order to access in-package files, whereas Node.js Compiler leaves them alone and instead works on a deeper level via libsquash. Pkg uses JSON to store in-package files while Node.js Compiler uses the more sophisticated and widely used SquashFS as its data structure.
EncloseJS	EncloseJS restricts access to in-package files to only five `fs.` API's, whereas Node.js Compiler supports all `fs.` API's. EncloseJS is proprietary licensed and charges money when used while Node.js Compiler is MIT-licensed and users are both free to use it and free to modify it.
Nexe	Nexe does not support dynamic `require` because of its use of `browserify`, whereas Node.js Compiler supports all kinds of `require` including `require.resolve`.
asar	Asar uses JSON to store files' information while Node.js Compiler uses SquashFS. Asar keeps the code archive and the executable separate while Node.js Compiler links all JavaScript source code together with the Node.js virtual machine and generates a single executable as the final product.
AppImage	AppImage supports only Linux with a kernel that supports SquashFS, while Node.js Compiler supports all three platforms of Linux, macOS and Windows, meanwhile without any special feature requirements from the kernel.