├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE └── README.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@bnb.im. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms. 4 | 5 | 6 | ## Important! 7 | > The pull request should have a useful title. Pull requests with `Update readme.md` as title will be closed right away because I'm so tired of nobody reading this document. Please carefully read everything in `Adding to this list`. 8 | 9 | ## Table of Contents 10 | 11 | - [Adding to this list](#adding-to-this-list) 12 | - [Adding something to an awesome list](#adding-something-to-an-awesome-list) 13 | - [Updating your Pull Request](#updating-your-pull-request) 14 | 15 | ## Adding to this list 16 | 17 | Please ensure your pull request adheres to the following guidelines: 18 | 19 | - Search previous requests for additions to `awesome-awesome-nodejs` before making a new one - your request may be a duplicate. 20 | - Make an individual pull request for each suggestion to `awesome-awesome-nodejs`. 21 | - All awesome lists added to `awesome-awesome-nodejs` should be in the [master awesome list](https://github.com/sindresorhus/awesome). If they're not already, now's a *great* time to add them! 22 | - Suggestions for improvements to the awesome list are _always_ welcome. 23 | - Check your spelling and grammar. 24 | - Make sure your text editor is set to remove trailing whitespace. 25 | - The pull request and commit should have a useful title. 26 | 27 | Suggestions for ammendments to these guidelines are always welcome - feel free to submit an issue or pull request. 28 | 29 | ## How to: Add a Node.js awesome list to to awesome-awesome-nodejs 30 | 31 | If you have something awesome to contribute to awesome-awesome-nodejs list, this is how you can do it. 32 | 33 | You'll need to have a GitHub account - you can [register here](https://github.com/join)! 34 | 35 | 1. Access awesome-awesome-nodejs's GitHub page [here](https://github.com/bnb/awesome-awesome-nodejs) 36 | 2. Click on the `README.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png) 37 | 3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png) 38 | 4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png) 39 | 5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png) 40 | 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! 41 | 42 | ## Updating your Pull Request 43 | 44 | Sometimes, the maintainers of awesome-awesome-nodejs will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-awesome-nodejs list guidelines. We're always happy to help in any way we can. 45 | 46 | [Here](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. 47 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Awesome Awesome Node.js [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome) 2 | 3 | > A curated list of awesome lists that are about or related to Node.js. 4 | 5 | *Inspired by the [awesome](https://github.com/sindresorhus/awesome) list thing, going deeper down the rabbit hole. 🐰* 6 | 7 | #### Meta stuff about this awesome list: 8 | If you'd like to add an awesome list to `awesome-awesome-nodejs` that's related to Node.js, be sure to read the [contribution guidelines](CONTRIBUTING.md) and then make your change and [open a pull request](https://opensource.guide/how-to-contribute/#opening-a-pull-request)! 9 | 10 | Be sure to check out the official [Node.js website](https://nodejs.org) and the [Node.js GitHub organization](https://github.com/nodejs) if you'd like to get involved. Find the original article that sparked this list on the [NodeSource Blog](https://nodesource.com/blog/the-21-most-awesome-awesome-lists-for-node-js-developers/). 11 | 12 | Like `awesome-awesome-nodejs`? Reach out to [@bitandbang](https://twitter.com/bitandbang) on Twitter to say *hi*! 👋 13 | 14 | 19 | 20 | ## Table of Contents 21 | - [Awesome Node.js Lists](#awesome-nodejs-lists) 22 | - [Awesome JavaScript Lists](#awesome-javascript-lists) 23 | - [Awesome Deployment Lists](#awesome-deployment-lists) 24 | - [Awesome Tool, Framework, and Protocol Lists](#awesome-tool-framework-and-protocol-lists) 25 | - [Awesome Ecosystem Lists](#awesome-ecosystem-lists) 26 | 27 | ## Awesome Node.js Lists 28 | Know of an awesome list that would fit in this section? [Help add it!](https://github.com/bnb/awesome-awesome-nodejs/issues/new) 29 | 30 | * [Node.js](https://github.com/sindresorhus/awesome-nodejs) - The core awesome list for Node.js. 31 | * [npm](https://github.com/sindresorhus/awesome-npm) - A list specifically around npm, the package manager bundled with Node.js by default. 32 | 33 | ## Awesome JavaScript Lists 34 | Know of an awesome list that would fit in this section? [Help add it!](https://github.com/bnb/awesome-awesome-nodejs/issues/new) 35 | 36 | * [JavaScript](https://github.com/sorrycc/awesome-javascript) - A central list of _everything_ JavaScript. 37 | * [ES6 Tools](https://github.com/addyosmani/es6-tools) - Collection of tooling around enabling ES6 features. 38 | * [Functional Programming](https://github.com/stoeffel/awesome-fp-js) - An extensive list of resources on learning, implementing, and using Functional Programming in JavaScript. 39 | * [Promises](https://github.com/wbinnssmith/awesome-promises) - A list with a focuses on resources, implementations, and utilities for Promises. 40 | * [JavaScript Learning](https://github.com/micromata/awesome-javascript-learning) - A list limited to the best learning resources about JavaScript – the language. 41 | 42 | ## Awesome Deployment Lists 43 | Know of an awesome list that would fit in this section? [Help add it!](https://github.com/bnb/awesome-awesome-nodejs/issues/new) 44 | 45 | * [Linux Containers](https://github.com/Friz-zy/awesome-linux-containers) - One of the most comprehensive lists of resources surrounding containers and containerization you'll find. 46 | * [Amazon Web Services (AWS)](https://github.com/donnemartin/awesome-aws) - AWS is a de facto choice for deploying Node.js apps to the cloud - fantastic resources around deploying with AWS. 47 | * [Docker](https://github.com/veggiemonk/awesome-docker) - Everything about Docker, from general articles to community meetups. 48 | * [Kubernetes](https://github.com/ramitsurana/awesome-kubernetes) - A bountiful resource to begin orchestrating containerized applications with Kubernetes. 49 | 50 | ## Awesome Tool, Framework, and Protocol Lists 51 | Know of an awesome list that would fit in this section? [Help add it!](https://github.com/bnb/awesome-awesome-nodejs/issues/new) 52 | 53 | * [Electron](https://github.com/sindresorhus/awesome-electron) - A suite of of resources for building with [Electron](electron.atom.io). 54 | * [React](https://github.com/enaqx/awesome-react) - List of resources for React, covering just about every concept, methodology, and implementation in the React ecosystem. 55 | * [React Native](https://github.com/jondot/awesome-react-native) - Comprehensive collection of resources React Native. 56 | * [Webpack](https://github.com/d3viant0ne/awesome-webpack) - Curated list of Webpack loaders, integrations, articles, videos, examples, and more. 57 | * [Vue](https://github.com/vuejs/awesome-vue) - Selection of both official and community Vue.js examples, tooling, snippets, components, and projects. 58 | * [ESLint](https://github.com/dustinspecker/awesome-eslint) - List around everything ESLint. You should be linting if you're not already 😉 59 | * [TypeScript](https://github.com/dzharii/awesome-typescript) - Everything TypeScript, including essential resources, plugins, and tools. 60 | * [Maintenance Modules](https://github.com/maxogden/maintenance-modules) - _Tiny_ set of mostly tiny modules, all built to improve the experience of developing and maintaining modules. 61 | 62 | ## Awesome Ecosystem Lists 63 | These are lists that don't necessarily fit in one of the above categories, but 64 | 65 | * [Chrome DevTools](https://github.com/ChromeDevTools/awesome-chrome-devtools) - Compilation of a variety of projects based on the Chrome DevTools tooling, by the DevTools team. 66 | * [Mad Science npm Packages](https://github.com/feross/awesome-mad-science) - Mad science packages, published on npm, that push the bounds of what JavaScript, Node.js, and a suite of other web technologies can do. 67 | * [Network-layer JavaScript](https://github.com/Kikobeats/awesome-network-js) - Networking tools, modules, and protocol implementations built with JavaScript and Node.js that enable developers to build against a variety of network layers. 68 | * [Awesome micro npm packages](https://github.com/parro-it/awesome-micro-npm-packages) - Small, focused npm packages that do one thing well. 69 | --------------------------------------------------------------------------------