As originally proposed in the first requirements doc for Wing, we would like Wing libraries to be JSII libraries. This would enable existing JSII tooling like jsii-pacmak to be used to convert Wing libraries into libraries for other languages like Python, Java, etc.
Proposed Solution
Emit a .jsii file inside the tarball produced by wing pack.
Implementation Notes
No response
Component
Compiler, CLI
Community Notes
Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.
If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out on the #dev channel in the Wing Discord.
Use Case
As originally proposed in the first requirements doc for Wing, we would like Wing libraries to be JSII libraries. This would enable existing JSII tooling like jsii-pacmak to be used to convert Wing libraries into libraries for other languages like Python, Java, etc.
Proposed Solution
Emit a
.jsiifile inside the tarball produced bywing pack.Implementation Notes
No response
Component
Compiler, CLI
Community Notes