[PR #1475] [MERGED] Improve Node.js description #9731

New Issue

GiteaMirror · 2026-04-19T03:59:25-05:00

GiteaMirror commented

2026-04-19 03:59:25 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1475
Author: @jjangga0214
Created: 12/11/2018
Status: ✅ Merged
Merged: 12/12/2018
Merged by: @sindresorhus

Base: master ← Head: patch-1

📝 Commits (2)

722b952 Update simple description of Node.js
511b966 Update readme.md

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 readme.md (+1 -1)

📄 Description

I added 'Asyncronous non-blocking event-driven' in front of the original description. I think they are core characteristics of Node.js, so this will more precisely depict what actually Node.js is, without loosing brevity. Also, these words are used on the first line of introduction on official Node.js website. What's more, by this update, someone who searches something like "async non-blocking framework" might find this repository.

By the way, I reviewed #1431 and #628.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
I have read and understood the instructions for creating a list.
This pull request has a descriptive title in the format Add Name of List (Example: Add Swift), not Update readme.md or Add awesome list.
The entry in the Awesome list should:
- Include a short description about the project/theme of the list. It should not describe the list itself.
  Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
- Be added at the bottom of the appropriate category.
The list I'm submitting complies with the below requirements.

I REMOVED THE SECOND SECTION OF PR TEMPLATE FOR SAVING SCROLLING HEIGHT AS THIS PR IS FOR UPDATE

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/1475 **Author:** [@jjangga0214](https://github.com/jjangga0214) **Created:** 12/11/2018 **Status:** ✅ Merged **Merged:** 12/12/2018 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`722b952`](https://github.com/sindresorhus/awesome/commit/722b952c6b7593a5731feea645323b3fa58c519c) Update simple description of Node.js - [`511b966`](https://github.com/sindresorhus/awesome/commit/511b966334e2556765a7b96bbd89b367830b0005) Update readme.md ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -1) </details> ### 📄 Description I added *'Asyncronous non-blocking event-driven'* in front of the original description. I think they are core characteristics of Node.js, so this will more precisely depict what actually Node.js is, without loosing brevity. Also, these words are used on the first line of [introduction on official Node.js website](https://nodejs.org/en/about/). What's more, by this update, someone who searches something like "async non-blocking framework" might find this repository. By the way, I reviewed #1431 and #628.   ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** ## Requirements for your pull request - **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. - I have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). - This pull request has a descriptive title in the format `Add Name of List` (Example: `Add Swift`), not `Update readme.md` or `Add awesome list`. - The entry in the Awesome list should: - Include a short description about the project/theme of the list. **It should not describe the list itself.**<br>Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`. - Be added at the bottom of the appropriate category. - The list I'm submitting complies with the below requirements. **I REMOVED THE SECOND SECTION OF PR TEMPLATE FOR SAVING SCROLLING HEIGHT AS THIS PR IS FOR UPDATE** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-19 03:59:25 -05:00

GiteaMirror closed this issue

2026-04-19 03:59:26 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#9731