Open
Conversation
BridgeJS: Adjust for the latest top-level requirement for `@_extern(wasm)`
BridgeJS: Extend snapshot test setup for exports <-> global this by including mixed module test case
…mespace BridgeJS: exposeToGlobal configuration option to control declare global declaration
… reversed order and intermediate properties
…rameters BridgeJS: Fix ordering issue with multiple stack based parameters
* PackageToJS: Make some options optional in option setup functions * Examples: Add NodeJS example * Documentation: Add Package output structure article * Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Revert browser.d.ts API change --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
BridgeJS: Enable struct as default parameter and enable default parameters in struct init / methods
BridgeJS: Struct and struct vs classes benchmarks
…nches and extracting helpers
NFC: BridgeJS: Simplify ExportSwift codegen by removing redundant branches and extracting helpers
NFC: BridgeJS: Further simplify codegen and JSValue intrinsics
Fix ts2swift alias struct naming and docs
BridgeJS: Consolidate optional and pointer runtime intrinsics
Benchmarks: Prevent cross-module inlining of f32/f64 @_extern(wasm) functions
…ure gates (#630) * BridgeJS: Make `@JSClass`, `@JSFunction`, etc generally available without @_spi(Experimental) * BridgeJS: Remove JAVASCRIPTKIT_EXPERIMENTAL_BRIDGEJS feature gate * BridgeJS: Update documentation for MVP release * [skip ci] Update READMEs
…631) Extends the fix from b3ddd88 (which addressed f32/f64) to all remaining public @_extern(wasm) BridgeJS intrinsics: i32, string, pointer, throw, init_memory, and struct_cleanup. Without @inline(never) wrappers, the Swift compiler can inline these functions across module boundaries, causing the wasm import module attribute to change from "bjs" to "env". This results in a wasm-ld linker error when a downstream module (e.g. via BridgeJS codegen) references the same symbol with a different import module. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
To make push/pop operations agnostic to import/export contexts, rename the following methods: - `bridgeJSLiftParameter()` -> `bridgeJSStackPop()` - `bridgeJSLowerStackReturn()` -> `bridgeJSStackPush()`
…mory` (#635) This allows us to insert cleanup code for String parameter passing for JS -> Swift.
TS2Swift: Make it easier to use ts2swift directly
…ease BridgeJS: Fix double-release of JSObject when passing a `JSObject?` JS->Swift
…ce-dirs BridgeJS: Include pluginGeneratedSources in build plugin input files
…writes BridgeJS: Skip writing output files when content is unchanged
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 : )