node-deep-equal
shelljs
node-deep-equal | shelljs | |
---|---|---|
2 | 27 | |
760 | 14,155 | |
0.3% | 0.3% | |
8.0 | 6.4 | |
4 months ago | 3 months ago | |
JavaScript | JavaScript | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-deep-equal
-
Unreasonable interview question?
This is a pretty hard problem, there are lot's of subtleties even just in defining deep equality. A quick check of a run of the mill implementation will confirm that this is not a problem for a junior: https://github.com/inspect-js/node-deep-equal/blob/master/index.js
-
Do you want to become a better maintainer?
So I got a bit curious to look even deeper to this and noticed qs is not the only case where the similar fate has happened. Another package using side-channel is deep-equal and has a similar history. It used to be a very small utility when still in v1.0 series, but starting from v1.1 it had new maintainers and the package size went up while also having performance regressions so people kept using v1.0.
shelljs
-
The Bun Shell
When I need shell-like utilities from my JS scripts I've previously used shelljs [0]. It's neat that Bun is adding more built-in utilities though.
[0] https://github.com/shelljs/shelljs
-
Auto commit with LaunchAgents & JavaScript
Now we can open this new project and we're going to install one package, shelljs Shelljs is a great Command Line Utility for interacting with the command line in JavaScript.
-
zx 7.0.0 release
Feels like this library is trying to solve a problem solved long ago by shelljs
-
Guide: Hush Shell-Scripting Language
The purpose of OP's project kind of reminded me of shell.js (shx) [1] which is a nodejs library that wraps all kinds of common UNIX commands to their own synchronously executed methods.
I guess that most shell projects start off as wanting to be a cross-platform solution to other operating systems, but somewhere in between either escalate to being their own programming language (like all the powershell revamps) or trying to reinvent the backwards-compatibility approach and/or POSIX standards (e.g. oil shell).
What I miss among all these new shell projects is a common standardization effort like sh/dash/bash/etc did back in the days. Without creating something like POSIX that also works on Windows and MacOS, all these shell efforts remain being only toy projects of developers without the possibility that they could actually replace the native shells of Linux distributions.
Most projects in the node.js area I've seen migrate their build scripts at some point to node.js, because maintaining packages and runtimes on Windows is a major shitshow. node.js has the benefit (compared to other environments) that it's a single .exe that you have to copy somewhere and then you're set to go.
When I compare that with python, for example, it is super hard to integrate. All the anaconda- or python-based bundles for ML engineers are pretty messed up environments on Windows; and nobody actually knows where their site-packages/libraries are really coming from and how to even update them correctly with upstream.
[1] https://github.com/shelljs/shelljs
-
Change working directory in my current shell context when running Node script
`` When I then run this file with./bin/nodefile`, it exits, but the working directory of the current shell context has not changed. I have also tried shelljs, but that does not work either.
-
Ask HN: Let's Build CheckStyle for Bash?
Oh people have tried - here are a few https://stackoverflow.com/questions/10239235/are-there-any-l...
I vaguely remember quite liking bish when I saw it years ago https://github.com/tdenniston/bish but it looks like no commits in 6 years.
This shelljs thing looks more promising, but really tedious to use https://github.com/shelljs/shelljs - shell.rm('-rf', 'out/Release'); I'd rather suffer proper bash than have to do that sort of thing.
Nothing seems to have really caught on so far. Bash is easy to learn and hack on, and before you know it, that simple install.sh that started out moving a few files around is 5000 lines, unmaintainable, and critical to bootstrapping your software :)
-
Release of google/zx 5.0.0
I personally prefer shelljs for stuff like this. zx seems pretty high on the "insane syntactic sugar" train.
-
How to build a CLI using NodeJS 💻
As we are creating starter files, let's use ShellJS to run commands like git clone, mkdir...
-
shelljs VS bargs - a user suggested alternative
2 projects | 7 Dec 2021
-
Scripting Languages of the Future
This talks a bunch about the "good run" of current scripting languages, including for example JavaScript.
But JavaScript, as an actual scripting language, has been pretty primitive but finally starting to become a real candidate for actual scripting. There's imo crufty not very great options like shelljs[1]. But adding a tagged-template string for system(), for calling things, and a little bit of standard library has made JS a much more interesting & competent scripting language. Those efforts are being done in ZX[2].
I like the idea of the topic, exploring it. But the author feels off in a number of places.
> What TypeScript showed is that you could join together the idea of a flexible lightweight (and optional!) type system onto an existing programming language, and do so successfully. . . .The question then is - what if you created a programming language from the start to have this kind of support?
Personally I just don't think languages matter very much. They're very similar, by & large. They have different tooling, packaging, somewhat different looks/feels for executing code, and their standard libraries are different. But TypeScript is popular & fast at least 90% because it is JS, because it works with JS things. Arguing that we should try to recreate TypeScript apart from JS sounds like a mind blowing waste of time. Also, Deno has good integrated TypeScript support.
On the topic of easy parallelism, JavaScript promises are imo quite easy to stitch together & use & quite available.
One of the main issues I see with easy-parallelism is that it's too easy: there's too many cases for uncontrolled parallelism. Throwing tarn.js or other worker-pools at problems seems all too common. But one is still left stitching together each pool/stage of work. I'd like to see SEDA[3] like architectures emerge, and perhaps get added to something like ZX standard library.
[1] https://github.com/shelljs/shelljs
[2] https://github.com/google/zx
[3] https://en.wikipedia.org/wiki/Staged_event-driven_architectu...
What are some alternatives?
fast-deep-equal - The fastest deep equality check with Date, RegExp and ES6 Map, Set and typed arrays support
zx - A tool for writing better scripts
mocha - ☕️ simple, flexible, fun javascript test framework for node.js & the browser
Inquirer.js - A collection of common interactive command line user interfaces.
ava - Node.js test runner that lets you develop with confidence 🚀
cross-env
assertnever - Syntactical sugar for assert never
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
node - Node.js JavaScript runtime ✨🐢🚀✨
chalk - 🖍 Terminal string styling done right
sudo-block - Block users from running your app with root permissions
ora - Elegant terminal spinner