JavaScript Repositories I Follow
Tags: javascript, github, githunt
Published: 2019-01-14 12:35:43

Before you start reading this article, I'm so sorry for my grammar mistakes. I'm not good at English. I'm saying this because I got criticism for my previous article.

{% twitter 1084095314015985665 %}

He was right. Really. I try to improve myself every day. Anyway. When I learn something new, I share it immediately.

*I [published](https://aligoren.com/javascript-repositories-i-follow/) this article on my own blog before*

Hi. For a while, I’m trying to follow some educational repositories. These are really useful repositories.

Maybe you’ve heard of them before. This is an article for people who ask where to start. Anyway.

## Before Starting

The following list is not ordered. It’s good if you can follow them all. So, you don’t have to start with the first one.

## Awesome JavaScript

🐢 A collection of awesome browser-side JavaScript libraries, resources, and shiny things.

This repository categorized the topics. For example, you need to something about routing, you can easily navigate to its subtopics. I found the **page.js** router thanks to this repo. There you can find many popular frameworks, libraries, and other awesome lists.

**Repo URL:** [https://github.com/sorrycc/awesome-javascript](https://github.com/sorrycc/awesome-javascript)

## You Don’t Know JS

You should be heard this repo. You probably heard this repo. This is a book series on JavaScript. There are six books to be master of the JavaScript **(Okay, this completely depends on you)**. It’s completely free.

![](https://thepracticaldev.s3.amazonaws.com/i/uxewqt45d67e0ixaq9fy.PNG)

**Repo URL:** [https://github.com/getify/You-Dont-Know-JS](https://github.com/getify/You-Dont-Know-JS)

## Front-End Checklist

🗂 The perfect Front-End Checklist for modern websites and meticulous developers

You still think you have insufficient knowledge? I know that some developers think so. Even I think so. Because I don’t know everything.

Anyway, there are some rules to be observed like meta tags, attributes etc. These aren’t strict rules. But if you want to be a good front-end dev, you should know these rules. There you can find some hints about how to build more efficient websites.

![](https://thepracticaldev.s3.amazonaws.com/i/pje1t3em0ci951mmx309.PNG)

**Repo URL:** [https://github.com/thedaviddias/Front-End-Checklist](https://github.com/thedaviddias/Front-End-Checklist)

## 33 JS Concepts

📜 33 concepts every JavaScript developer should know.

As you understand, there are 33 concepts you should know. Also available in different languages. By this repository, you can easily understand what’s the difference between **==** and **===**.

![](https://thepracticaldev.s3.amazonaws.com/i/8bkne077kryq125gkbjw.PNG)

**Repo URL:** [https://github.com/leonardomso/33-js-concepts](https://github.com/leonardomso/33-js-concepts)

## Modern JS Cheatsheet

Cheatsheet for the JavaScript knowledge you will frequently encounter in modern projects.

With this repository, you will get the explanation of JavaScript features. Everything is simply explained. Each topic is exemplified by code snippets.

![](https://thepracticaldev.s3.amazonaws.com/i/ax2ghzjfg7x5fpbrt92a.PNG)

**Repo URL:** [https://github.com/mbeaudru/modern-js-cheatsheet](https://github.com/mbeaudru/modern-js-cheatsheet)

## Clean Code JavaScript

🛁 Clean Code concepts adapted for JavaScript

Actually, these are the techniques to be followed by every developer in every language. In this repo, examples are created on JavaScript. Naming, arguments, meaningful code snippets are important. For example, what does this code do?

```javascript
function ok(a, a1, a2) {
   // some code will be here.
}
```

What is the **“ok“**? Why there are three arguments? What should I understand by **a, a1** and **a2**? Developers are asking questions when they see a code snippet like this. There you can find some techniques to write more clean code.

![](https://thepracticaldev.s3.amazonaws.com/i/id4xcpltnuzix3xq8ani.PNG)

**Repo URL:** [https://github.com/ryanmcdermott/clean-code-javascript](https://github.com/ryanmcdermott/clean-code-javascript)

## JavaScript Style Guide by Airbnb

This is one of the most famous style guides.

Which one I should use? “var”, “const” or “let” and why? you can find answers for this kind questions. An example about quote using.

```javascript
// bad
const bad = {
  'foo': 3,
  'bar': 4,
  'data-blah': 5,
};
 
// good
const good = {
  foo: 3,
  bar: 4,
  'data-blah': 5,
};
```

With this style guide, you can more readable codes. These aren’t strict rules. But every JavaScript developer should know what are they. My friend working for a big company. They using this style guide their projects. So every developer in that team is using this style guide.

![](https://thepracticaldev.s3.amazonaws.com/i/33073qxvtj3iqayl5upj.PNG)

**Repo URL:** [https://github.com/airbnb/javascript](https://github.com/airbnb/javascript)

I hope this article will help you.

Thanks for reading.