Notices by gibwar (gibwar@mastodon.social)

@nikitonsky don't get too comfortable with it, it's being removed from node.js distributions. See https://eluminoustechnologies.com/blog/news/node-js-removes-corepack/ and https://socket.dev/blog/node-js-takes-steps-towards-removing-corepack for more info.

@aral certainly! Feel free to ping me if you have any questions. I use both PowerShell and node pretty heavily (as well as Windows) so I've been around the issues a time or two!

@aral I'm sure there's reasons you ended up on this result. If you didn't come across it, you can base64 encode a command for PowerShell and pass it in via the -EncodedCommand to not have to worry about multiple levels of quoting through shells. I'm a little worried about the comment on spaces in paths, node should be able to handle them just fine.

A recommendation is to use spawnSync instead and pass in a proper argument array which will work around the need to spawn a shell and quoting issues