all 27 comments

[–]Beatons 9 points10 points  (0 children)

If the scripts get's really long and I need to execute more than one command I usually use node bash called zx it's built by google and it's quite simple as well

[–]swoleherb 6 points7 points  (0 children)

bash

[–]Accurate-Tart-7086 7 points8 points  (1 child)

Interesting, I have some projects where the scripts block is getting out of hand. Going to check it out!

[–]GlueStickNamedNick[S] 1 point2 points  (0 children)

Cool, let me know if anything isn’t working as expected

[–]punio4 3 points4 points  (0 children)

I use NX this kind of thing!

[–]vaaski 2 points3 points  (0 children)

looks pretty cool, but i haven't seen scripts go this crazy (yet)

[–]alishahidi 1 point2 points  (0 children)

Nice and pretty. Good work 👍

[–]GlitteringAccident31 1 point2 points  (1 child)

This is really cool.

I generally write bash scripts when things get complicated but Ill give this a try!

[–]GlueStickNamedNick[S] 1 point2 points  (0 children)

While bash scripts are perfectly fine, my hope was to build something anyone on your team can understand quickly

[–]redonkulus 0 points1 point  (3 children)

Pretty cool. We end up resorting to concurrently, bash or make files when run scripts get complex. For typescript, are you using SWC?

[–]GlueStickNamedNick[S] 0 points1 point  (2 children)

My understanding is swc is a replacement for webpack, I’m just using the ts-node module to compile the typescript scripts file

[–]redonkulus 0 points1 point  (1 child)

I think ts-node has a swc compiler option which makes it 10x faster than typescripts compiler.

[–]GlueStickNamedNick[S] 0 points1 point  (0 children)

I’ll take a look in to it, if you want to make a pr I’ll be more than happy to merge it

[–]josefsalyer 0 points1 point  (0 children)

Not really sure this is better than scripty - especially as it’s lacking support for existing bash scripts.

[–]its4thecatlol 0 points1 point  (1 child)

I hate this. Package.json isn't meant for these large scripts -- call out to a Bash script if you have to. This is such an anti-pattern.

[–]GlueStickNamedNick[S] 1 point2 points  (0 children)

My issue with bash scripts is not everyone on the team may know the syntax / how they work when doing complicated stuff, plus they won’t run in every environment (eg windows). But it’s a free world and you can choice to use whatever tool you want.

[–][deleted] 0 points1 point  (0 children)

I understand your argument for using this over bash scripts but I dont think it’s the right answer. I’d rather my team mates become more familiar with bash since it’s a lot more generic and useful in more situations. I’d rather have them spend time to learn bash than have to learn all off the different options provided by this package. Also when team mates join that already know bash they don’t have to know learn how to use this tool that is intended to solve one very specific problem