Max Desiatov

Potential API for the package to be callable from other build tools (suggested by @ephemer) ```javascript const carton = require("carton"); carton.build("/package/to/package.swift").then(result => { console.log(result.wasmPath) console.log(result.javascriptSource) }); ```

I've created [a basic template repository](https://github.com/swiftwasm/browser-basic-template), which also has a textual introduction with links for beginners, and a working test suite. Still need a similar template for [Tokamak](https://tokamak.dev).

Yes, totally! 👍 I think we'd keep `basic` and `tokamak` as aliases for two corresponding repositories, but would be great to support what you've described as a general form. For...

I have no idea how packaging works on Ubuntu/Debian, but would it be possible to create a symlink from `swift-carton` to the real `carton` binary installed in some other folder...

I see there's a way to setup diversions here, could that work? https://linux.die.net/man/8/dpkg-divert

Another solution is to specify a conflict with the Perl package, as Mono people have done here https://github.com/mono/mono/issues/9056#issuecomment-532951039

BTW, is it an established practice to maintain Linux distro packaging scripts in a separate repository or in the main upstream source repository? I wouldn't mind keeping the packaging scripts...

Hi @jankaltoun, thanks for reporting this issue. Are you executing `carton dev` from a directory that has `Package.swift` in it? Currently `carton` is only able to build SwiftPM packages with...

No problem at all! I'll keep the issue open until `carton` is able to detect that `Package.swift` is missing in the current directory and the error message is improved. 🙂

@tscholze have you been able to debug your app with the demangled stack trace? Can this issue be closed?