Our project currently utilizes the pkg npm package to generate binaries. However, 'pkg' has been archived and is no longer maintained, which may lead to potential security vulnerabilities and compatibility issues.
Objective:
Identify and integrate a robust, actively maintained alternative to 'pkg' for binary generation, ensuring the continued reliability and security of our project.
Considerations:
Active Maintenance: The alternative should have regular updates and an active community to address emerging issues and security concerns.
Feature Parity: The new solution should offer comparable functionality to 'pkg', including support for packaging Node.js applications into standalone executables.
Compatibility: Ensure that the alternative is compatible with our project's existing codebase and build processes. In the past, we have had some headache with packaging tree-sitter.
Next Steps:
Research: Find and evaluate potential alternatives, focusing on their maintenance status, feature sets, and community support.
Testing: Implement a proof-of-concept using the selected alternative to ensure it meets our project's requirements.
Integration: Replace 'pkg' with the chosen solution in our build process, updating documentation and build scripts as necessary.
erbesharat
commented
3 weeks ago
Description:
Our project currently utilizes the pkg npm package to generate binaries. However, 'pkg' has been archived and is no longer maintained, which may lead to potential security vulnerabilities and compatibility issues.
Objective:
Identify and integrate a robust, actively maintained alternative to 'pkg' for binary generation, ensuring the continued reliability and security of our project.
Considerations:
Next Steps: