-
-
Notifications
You must be signed in to change notification settings - Fork 45
Publish carton
as npm package
#336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A side benefit of this would be that anyone with Node installed would be able to run |
FWIW: wasm-pack provides similar package https://github.com/rustwasm/wasm-pack/tree/master/npm |
We need to take into account swiftlang/swift-package-manager#3905. Until that's merged, we'll have to build with |
Potential API for the package to be callable from other build tools (suggested by @ephemer) const carton = require("carton");
carton.build("/package/to/package.swift").then(result => {
console.log(result.wasmPath)
console.log(result.javascriptSource)
}); |
In theory, this should allow us to distribute self-contained binaries on Linux. These wouldn't be statically linked completely, but at least they should no longer depend on a separate dynamic library file with Swift stdlib. Related to #336.
It now became a SwiftPM Plugin, so don't need to publish it as npm package now. |
Based on a discussion with one of our users, it would make sense to publish
carton
on npm, similarly to howesbuild
orswc
provide binaries on npm. This would allow users primarily relying on npm to integratecarton
and its commands into their npm-based workflow.The text was updated successfully, but these errors were encountered: