Go doesn't need glob/fx-extra as the standard library already has those capabilities, it also has support for generics and there are multiple packages to do console coloring, like github.com/gookit/color
In my impression, the glob/fs api of the standard library is difficult to use, the former does not support deep matching, such as matching packages/**/package.json while ignoring node_modules, fs lacks a more convenient api, For example pathExists/readJson/writeJson etc. Also, generics are just out now, and I'm also waiting to see if someone creates a collection-related toolkit. At the moment, I can only use for of and it's hard to use. It makes me feel like I'm writing c language...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Go doesn't need glob/fx-extra as the standard library already has those capabilities, it also has support for generics and there are multiple packages to do console coloring, like github.com/gookit/color
In my impression, the glob/fs api of the standard library is difficult to use, the former does not support deep matching, such as matching
packages/**/package.jsonwhile ignoringnode_modules, fs lacks a more convenient api, For examplepathExists/readJson/writeJsonetc. Also, generics are just out now, and I'm also waiting to see if someone creates a collection-related toolkit. At the moment, I can only usefor ofand it's hard to use. It makes me feel like I'm writing c language...