rescript-stdlib-vendorer VS execa

~/rescript-project-template/src/Demo.res:1 Found "Js" module usage. Use the vendored standard library instead. Read more at: https://github.com/DZakh/rescript-stdlib-vendorer

One problem is that it suggests creating A.res, which is publicly available from other application parts. It’s usually fine for FE apps, but for developing BE and CLIs, I prefer to follow the hexagonal architecture by creating the implementation inside the Main.res and passing it to other modules via function arguments. Once again, an example from rescript-stdlib-vendorer:

I’m partial to Sindre Sorhus’ execa, this document outlines the differences:

https://github.com/sindresorhus/execa/blob/main/docs/scripts...

Yeah, or over https://github.com/sindresorhus/execa?

And given the existence of those npm packages, is there any aspect of Bun Shell that required it to be built into the Bun runtime instead of published to npm?

For something which works across all JS runtimes (Deno, Node) and achieves basically the same, check out the popular JS library Execa[1]. Works like a charm!

[1]: https://github.com/sindresorhus/execa

To simplify the process of running the commands, I will use execa - abstraction library on top of Node.js child_process methods.

Hello, this is an interesting problem. At https://stacktape.com (where we're creating a developer-friendly abstraction of AWS), we're recommending 2 options: - use a "deployment script" (basically a custom-resource lambda function that runs during the CloudFormation deployment). You can install prisma into it, and then execute the migration command from the lambda function using something like execa, if you're using Javascript/Typescript. You can easily do this with Stacktape anytime. - use a bastion (EC2) instance (deployed to the the VPC where your RDS db is). The cheapest instances cost ~4.5$/month, so it shoudln't be too costly. You can also securely connect to it using EC2 instance connect, that leverages IAM to grant permissions to connect to it. (this is something we're currently implementing as Stacktape, and will be ready in ~2 weeks).

For FE, it’s usually Cypress or Playwright; for BE, it’s to run a server and start sending requests; for CLI, I like the tool called execa.

Since version 6 execa is pure ES module. An attempt to import a package into NestJS project results in an error:

Essentially when I run this from my shell I get a listing of keymaps configured for vim. However, when I run it from a program without a PTY or TTY (e.g., via Rust's Command or Node's execa) I get an exit code of 0 and no output.