Yoshiya Hinosawa
Yoshiya Hinosawa
Set up files: ```shellsession $ touch file.txt $ ln -s file.txt link.txt ``` script: ```ts import { copy } from "@std/fs"; copy("link.txt", "link-copy.txt", { preserveTimestamps: true }); ``` ```shellsession $...
Is this common pattern in cli tool development? I personally don't often see the multiple spinners in cli tools in general.
Popular npm packages ([ora](https://www.npmjs.com/package/ora), [cli-spinners](https://www.npmjs.com/package/cli-spinners)) that implement spinners don't support multiple spinners. I'm skeptical the users need this feature. If we add this feature, I expect the added complexity won't...
(Sharing another point raised in an offline discussion.) When there are multiple things going on in CLI tools, I often see the single loading indicator with the message part changing...
The suggestion makes sense to me. Maybe we should use `format` of `std/internal` to make the expression?
> If not a browser, dynamically import node:os to check if on Windows. That should take care of Deno, Bun and Node. I'm not in favor of this as this...
I changed the commit type from `feat` to `refactor` as it's not tested with Node and Bun yet.
We can't ask somebody to test on every change. We need to set up CI to ensure it's working on specific platform.
I'd suggest we would make `feat(path): add support of Node` commit when we set up the CI on Node.
I changed the title a bit as there seem somethings remaining (like the usage of `Deno.cwd()`) to make `@std/path` truly compatible with Node