Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Jul 19, 2021

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 : )

@pull pull bot added ⤵️ pull merge-conflict Resolve conflicts manually labels Jul 19, 2021
@atomist atomist bot added auto-branch-delete:on-close Delete branch when pull request gets closed auto-merge-method:merge Auto-merge with merge commit auto-merge:on-bpr-success Auto-merge on passed branch protection rule labels Jul 19, 2021
@pull pull bot removed auto-branch-delete:on-close Delete branch when pull request gets closed auto-merge-method:merge Auto-merge with merge commit auto-merge:on-bpr-success Auto-merge on passed branch protection rule labels Jul 19, 2021
This suppresses warnings from swift-syntax
BridgeJS: Move intrinsic declarations to JavaScriptKit under SPI
BridgeJS: Add `throws(JSException)` to imported methods
Use of class type for `SwiftRuntime` in `instantiate.d.ts` makes it
difficult to union types of two `instantiate` variants.
PackageToJS: Use non-class type for SwiftRuntime in instantiate.d.ts
emsdk includes `node` directory but the `which` function returned it
as a valid executable.
Fix `which` not to return directories
…stry

In FinalizationRegistry mode, the `swjs_free_host_function` should
be called with the Swift heap object ID, not the JS closure object ID.
The wrong argument was causing:
- Swift closures to be leaked, because FinalizationRegistry attempted
  to release a JS object ID that was never registered as a Swift closure.
- Unintended deallocation of unrelated closures when a reused JS object ID
  happened to match a valid Swift closure ID by coincidence. This
  eventually led to crashes with `The JSClosure has been already released by Swift side.`
kateinoigakukun and others added 30 commits November 22, 2025 18:18
When generating `@_extern(wasm)` function declarations in the
BridgeJS plugin, we now need to ensure that they are placed at the
top level of the module, rather than nested within other declarations
because of the restrictions of the main branch Swift compiler.
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v5...v6)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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
…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
[NFC] BridgeJS: Codegen code organisation and minor cleanups
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants