bash
Nest
bash | Nest | |
---|---|---|
9 | 312 | |
583 | 64,525 | |
2.2% | 1.4% | |
5.8 | 9.9 | |
9 days ago | 4 days ago | |
C | TypeScript | |
GNU General Public License v3.0 only | MIT 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.
bash
-
Node.js 20 is now available
> Next you'll be telling me that I shouldn't use Bash because Bash 5.0 came out in 2018 and only got two minor point releases over the next 5 years. But that sounds dumb, huh?
What's dumb is not being able to tell the difference. It's not about the numbers.
https://git.savannah.gnu.org/cgit/bash.git/ shows there are constant updates. Things are being worked on. Your example proves my whole point. There are updates every year for many years.
Express? Not so. There are many gaps in its history. And for a tool like Express that has way more surface area it is in need of a lot more testing and updating e.g. if NodeJs changes something it breaks.
Does Bash need to make sure it works with HTTP3, Brotli or many other things that came out? No.
> Because for the most part - it doesn't need them.
Right, let's go back to the Stone Age. You don't need clothes either - just a leaf. You're just so dismissive on innovation then why bother? You don't even need NodeJs. Back to assembly and punch cards...
> Is an ignorant take.
Yes, yours. As shown above by your example.
> People promote it because it's a good tool.
And how do you know that? Where are the stats? Or people just google for NodeJs server, see the top response being Express and just do that. The cycle then repeats. Have people promoting it actually benchmarked, compared and investigated all the tools before making this informed decision? I'm sure you've heard from each and everyone 1 of them to know the answer eh.
-
Why is the bash package outdated?
If anyone else is wondering (but it's probably just me), "compatibility level 50" doesn't mean that Bash has a complicated feature-detection algorithm that places compatibility on a scale from 0 to 100%. "Level 50" just means compatibility with bash 5.0.
-
Can someone help me understand this code?
The bash shell also has code in it to check for this same magic number. This is because bash is also available on systems where the kernel doesn't do #! processing, but people would still want their scripts to behave in a predictable manner. You can see this in execute_cmd.c from the current bash source code.
-
Why does foreground job ignore job control signals when Bash is running as pid 1?
Well, have you looked at the bash source? The error message is around line 4481 in this file: https://github.com/bminor/bash/blob/master/jobs.c
-
locate-exit: make your script say which line and why it finished execution
Was it some ancient bug? I cant seem to find a mention of it in bash changelog
-
How are bash shell's functions like `history` are set up and executed?
Here is Bash's source code.
-
Suicide Linux
After I made the comment I actually decided to look up BASHs source code and here appears to be the part that handles errors if the filename is to be believed https://github.com/bminor/bash/blob/master/error.c
-
How do CP and MV work?
I present you a middle case: here's the source code for Gnu bash's cp command.
- I finally figured out C++ and I like it
Nest
-
NestJS tip: how to change HTTP server timeouts
When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:
-
Containerize your multi-services app with docker compose
Back: a graphQL server built with Nestjs
-
Full Stack Web Development Concept map
NestJS - opinionated more scalable, but harder to learn docs
-
Don't go all-in Clean Architecture: An alternative for NestJS applications
Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):
- Utilizando Testcontainers para Testes de IntegraĆ§Ć£o com NestJS e Prisma ORM
-
A Gentle Introduction to Containerization and Docker
Itās a text document that contains all the commands a user could call to assemble an image. Letās check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.
-
Scalable REST APIs with NestJS: A Testing-Driven Approach
describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });
-
Rust GraphQL APIs for NodeJS Developers: Introduction
In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:
-
A Step-by-Step Guide to Implement JWT Authentication in NestJS usingĀ Passport
The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.
-
From Frontend to Backend
That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/
What are some alternatives?
ngs - Next Generation Shell (NGS)
SailsJS - Realtime MVC Framework for Node.js
thefuck - Magnificent app which corrects your previous console command.
Koa - Expressive middleware for node.js using ES2017 async functions
phero - Full-stack type-safety with pure TypeScript
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
coreutils - upstream mirror
feathers - The API and real-time application framework
shell-safe-rm - š Safe-rm: A drop-in and much safer replacement of bash rm with nearly full functionalities and options of the rm command! Safe-rm will act exactly the same as the original rm command.
Ts.ED - :triangular_ruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline to make your code more readable and less error-prone. āļø Star to support our work!
server - :desktop_computer: Simple and powerful server for Node.js
Moleculer - :rocket: Progressive microservices framework for Node.js