Hi,
Thank you for maintaining QuickJS-kt—it’s a fantastic Kotlin Multiplatform wrapper for QuickJS! I’m opening this feature request to propose updating the embedded QuickJS engine to use QuickJS-NG, the modern community-driven fork of QuickJS.
Why QuickJS-NG?
QuickJS-NG is an actively maintained fork that provides:
- Enhanced ECMAScript 2023+ support and closer compliance with the latest JS standards
- Improved embedding APIs and richer feature set for embedder convenience
- Better cross-platform support, including first-class Windows compatibility
- Ongoing optimizations and active community contributions
- Minimal API incompatibilities with original QuickJS, making migration relatively straightforward
Benefits to QuickJS-kt users:
- Access to newer JavaScript language features and enhanced runtime improvements
- More frequent updates and fixes from an engaged maintainer community
- Stronger platform support for Kotlin Multiplatform targets
Given QuickJS-kt’s role as a multiplatform Kotlin wrapper, aligning with QuickJS-NG would future-proof it and provide users with a more modern, maintained JS engine.
If help is needed:
I’m happy to assist with testing, validations, or code contributions to facilitate this migration.
Thanks again for your work on this great library!
Hi,
Thank you for maintaining QuickJS-kt—it’s a fantastic Kotlin Multiplatform wrapper for QuickJS! I’m opening this feature request to propose updating the embedded QuickJS engine to use QuickJS-NG, the modern community-driven fork of QuickJS.
Why QuickJS-NG?
QuickJS-NG is an actively maintained fork that provides:
Benefits to QuickJS-kt users:
Given QuickJS-kt’s role as a multiplatform Kotlin wrapper, aligning with QuickJS-NG would future-proof it and provide users with a more modern, maintained JS engine.
If help is needed:
I’m happy to assist with testing, validations, or code contributions to facilitate this migration.
Thanks again for your work on this great library!