Socket
Socket
Sign inDemoInstall

quickjs-emscripten

Package Overview
Dependencies
0
Maintainers
1
Versions
57
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install
Previous12456Next

0.25.0-rc.2

Diff

jitl
published 0.25.0-rc.1 •

jitl
published 0.25.0-rc.0 •

jitl
published 0.24.0 •

Changelog

Source

v0.24.0

  • #127 Upgrade to quickjs 2023-12-09:

    • added Object.hasOwn, {String|Array|TypedArray}.prototype.at, {Array|TypedArray}.prototype.findLast{Index}
    • BigInt support is enabled even if CONFIG_BIGNUM disabled
    • updated to Unicode 15.0.0
    • misc bug fixes
  • #125 (thanks to @tbrockman):

    • Synchronizes quickjs to include the recent commit to address CVE-2023-31922.
  • #111 (thanks to @yourWaifu) ArrayBuffer and binary json encoding:

    • context.newArrayBuffer(bufferLike) creates an ArrayBuffer in the VM from a buffer-like object.
    • context.getArrayBuffer(handle) creates a view on an ArrayBuffer in the VM as a UInt8Array on the host.
    • context.encodeBinaryJSON(handle) encodes a QuickJS handle in QuickJS's binary format (like JSON.stringify)
    • context.decodeBinaryJSON(handle) decodes a QuickJS handle containing the binary format (like JSON.parse)
jitl
published 0.23.0 •

Changelog

Source

v0.23.0

  • #114 (thanks to @yar2001) improve stack size for ASYNCIFY build variants:
    • Change the default ASYNCIFY_STACK_SIZE from 4096 bytes to 81920 bytes. This equates to an increase from approximately 12 to 297 function frames. See the PR for more details.
    • QuickJSAsyncRuntime.setMaxStackSize(stackSizeBytes) now also adjusts the ASYNCIFY_STACK_SIZE for the entire module.
jitl
published 0.22.0 •

Changelog

Source

v0.22.0

  • #78, #105 (thanks to @ayaboy) add Symbol helpers context.newUniqueSymbol, context.newSymbolFor, as well as support for symbols in context.dump.

  • #104 BigInt support.

  • #100 Breaking change upgrade Emscripten version and switch to async import(...) for loading variants. We also drop support for older browsers and Node versions:

    • Node >= 16 is required
    • Safari >= 14.1 is required
    • Typescript >= 4.7 is recommended, but not required.
jitl
published 0.21.2 •

Changelog

Source

v0.21.2

  • #94 (thanks to @swimmadude66) allows QuickJS to create many more functions before overflowing.
jitl
published 0.21.1 •

Changelog

Source

v0.21.1

  • #66 (thanks to @BickelLukas) fixes ReferenceError when running in browser due to global.process
jitl
published 0.21.0 •

Changelog

Source

v0.21.0

  • #61 (thanks to @torywheelwright):
    • Add QuickJSRuntime.setMaxStackSize(stackSizeBytes) to protect against stack overflows.
    • Add option maxStackSizeBytes when creating runtimes.
  • Change default branch master to main.
  • Add option memoryLimitBytes when creating runtimes.
jitl
published 0.20.0 •

Changelog

Source

v0.20.0

This is a large release! The summary is:

  • There are several breaking API changes to align our abstractions with the underlying QuickJS library.
  • There's a new build variant build with Emscripten's ASYNCIFY that allows synchronous code inside QuickJS to use asynchronous code running on the host.
  • Both build variants have basic support for loading and evaluating EcmaScript modules, but only the ASYNCIFY variant can asynchronously load EcmaScript code.

New features

This release introduces class QuickJSRuntime. This class wraps QuickJS's JSRuntime* type:

JSRuntime represents a Javascript runtime corresponding to an object heap. Several runtimes can exist at the same time but they cannot exchange objects. Inside a given runtime, no multi-threading is supported.

  • QuickJSRuntime.newContext creates a new context inside an existing runtime.
  • QuickJSRuntime.setModuleLoader enables EcmaScript module loading.

This release renames QuickJSVm to class QuickJSContext, and removes some methods. The new class wraps QuickJS's JSContext* type:

JSContext represents a Javascript context (or Realm). Each JSContext has its own global objects and system objects. There can be several JSContexts per JSRuntime [...], similar to frames of the same origin sharing Javascript objects in a web browser.

QuickJSContext replaces QuickJSVm as the main way to interact with the environment inside the QuickJS virtual machine.

  • QuickJSContext.runtime provides access to a context's parent runtime.
  • QuickJSContext.evalCode now takes an options argument to set eval mode to 'module'.

There are also Asyncified versions of both QuickJSRuntime (QuickJSRuntimeAsync) and QuickJSContext (QuickJSContextAsync). These variants trade some runtime performance for additional features.

  • QuickJSRuntimeAsync.setModuleLoader accepts module loaders that return Promise<string>.
  • QuickJSContextAsync.newAsyncifiedFunction allows creating async functions that act like sync functions inside the VM.

Breaking changes

class QuickJSVm is removed. Most functionality is available on QuickJSContext, with identical function signatures. Functionality related to runtime limits, memory limits, and pending jobs moved to QuickJSRuntime.

Migration guide:

  1. Replace usages with QuickJSContext.
  2. Replace the following methods:
    • vm.hasPendingJob -> context.runtime.hasPendingJob
    • vm.setInterruptHandler -> context.runtime.setInterruptHandler
    • vm.removeInterruptHandler -> context.runtime.removeInterruptHandler
    • vm.executePendingJobs -> context.runtime.executePendingJobs
    • vm.setMemoryLimit -> context.runtime.setMemoryLimit
    • vm.computeMemoryUsage -> context.runtime.computeMemoryUsage

QuickJS.createVm() is removed.

Migration guide: use QuickJS.newContext() instead.

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc