Repository navigation
Conversation
…ce-dirs BridgeJS: Include pluginGeneratedSources in build plugin input files
…writes BridgeJS: Skip writing output files when content is unchanged
Also cover more access levels in `@JSFunction` tests.
…cope-fix BridgeJS: Use indirect _exports lookup in wrap functions
PackageToJS: Replace @ts-ignore with @ts-expect-error in templates
…bal-cleanup Runtime: Enforce prettier formatting, simplify find-global.ts
BridgeJS: Add runtime tests for `@JS class` to JSObject conversion
Also use `ProcessInfo.processInfo.arguments[0]` instead of `#filePath` to detect changes to the plugin executable, which is more robust to changes in the source file location.
PackageToJS: Rebuild bridge-js.js when BridgeJSLink is changed
BridgeJS: Fix SwiftHeapObject finalization registry leaks and double release
BridgeJS: Support custom exported type names
…ream BridgeJS: Support protocol refinement and constrained imports
BridgeJS: Support exporting protocol methods with async and throws
JavaScriptEventLoop: Add opt-in `yieldInterval` for host responsiveness
JavaScriptEventLoop: Avoid O(N^2) job queue insert for bursts of jobs
BridgeJS: Escape reserved words in exported function parameters
The UWASI platform wrappers imported `useAll` and `MemoryFileSystem`, so bundles always carried UWASI's in-memory file system and came out larger than the browser_wasi_shim default. Import `useStdio`, `useArgs`, `useEnviron`, `useClock`, `usePoll`, `useProc` and `useRandom` instead. File syscalls now return ENOSYS. With `--enable-code-coverage`, the Node wrapper adds `useMemoryFS`, because the test runner reads the coverage profile through `extractFile`. The browser wrapper never imports a file system.
* Runtime: Copy only the view's window in swjs_load_typed_array `new Uint8Array(typedArray.buffer)` views the whole backing `ArrayBuffer`, ignoring the `byteOffset` and `byteLength` of the view it was handed. A view with a non-zero offset (anything from `subarray`, or `new Uint8Array(buffer, offset, length)`) therefore arrives in the guest shifted by that offset, silently wrong rather than failing. It is also a memory-safety bug: `JSTypedArray.copyMemory(to:)` sizes the destination from the view's own `length`, so whenever the view is smaller than its backing buffer the runtime writes past the end of the destination and corrupts whatever follows it in linear memory. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Tests: Use Int32(bitPattern:) for the 0xDEADBEEF sentinel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )