You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we start using newer features, like BigInt, FinalizationRegistry etc, we should still allow targeting older browsers.
Proposed solution
I'm currently thinking we could make --environment option more granular, allowing users to specify browser versions or JS versions, similarly to how --target option of esbuild works. Based on this information, we could pass additional flags to JSKit build (namely JAVASCRIPTKIT_WITHOUT_WEAKREFS), enable/disable i64 transform etc.
Alternatives considered
Not sure if direct support in SwiftPM and Swift for something like this is on the table yet, I previously tried something similar with swiftwasm/swift-package-manager#373.
The text was updated successfully, but these errors were encountered:
Motivation
As we start using newer features, like
BigInt
,FinalizationRegistry
etc, we should still allow targeting older browsers.Proposed solution
I'm currently thinking we could make
--environment
option more granular, allowing users to specify browser versions or JS versions, similarly to how--target
option ofesbuild
works. Based on this information, we could pass additional flags to JSKit build (namelyJAVASCRIPTKIT_WITHOUT_WEAKREFS
), enable/disable i64 transform etc.Alternatives considered
Not sure if direct support in SwiftPM and Swift for something like this is on the table yet, I previously tried something similar with swiftwasm/swift-package-manager#373.
The text was updated successfully, but these errors were encountered: