Gomix is called https://glitch.com now

Hello Benjamin and happy new year 2020! @BBlackwo

We plan to release the 2019 JavaScript Rising Stars (see #40)

I'd like to know if you want to write about the AngularJS eco-system, like you did last year (#32).

We could add credits at the end of the section, mentioning "by Benjamin Blackwood" for example.

Thank you in advance!

I think it'd be important to know when a project started, if we have that data. Maybe just say "Created: March 2017" or "Created: December 2015". etc.

Hello, there!

With 2020 approaching, I would like to ask if there is going to be a JavaScript Rising Stars 2019 and, if so, if the Learning Resource category is coming back this year.

If you are looking for someone to write the intro for the category, I am available - I did the same last year, as I am involved in multiple projects in this category. Just let me know in advance!

Cheers!

Hey team,
Looks like you removed the GraphQL category from the 2023 edition?

Being featured in the category was a great source of pride for our community (Garph) until it was suddenly removed some weeks ago 😢

Any chance you could bring it back?

Rising Stars is a ranking list, but can also as an ecosystem overview.

So, I'm thinking about tools that automating code checking, that's really important for FE dev now

e.g.

• prettier 38k stars
• eslint 17k stars
• husky 20k stars

Hi bestofjs team!
Thank you for awesome website. ✨

I have a question.
Could we reuse data of this site? (and 2016)

I'm organizer of vue.js japan users group.
Currently, We are preparing for the conference event with non-profit and volunteer.
We want to provide the docs for sponsor.

I think it would be great to have the option to view in dark mode. Generally users prefer having the ability to use dark or light mode. Dark mode is a pretty common thing for most websites these days and having this option only makes the website more popular (Which we want!). I personally found my eyes getting a bit tired half way through the article. Also there was a comment from one of ThePrimeTime's viewers in his 2023 JS rising Stars video that inspired me to create this issue 😆

If dark mode is something we can add I would be interested in working on this and happy to discuss more 👍

Moving discussion to a new issue

Hey @michaelrambeau i think that adding a "Miscellaneous" category (ie: Anything that doesn't fit in any other categories) would be a great addition. As a very curious person, I would love to see that. This way it could cover a lot of things (Chatbots, Animations etc..)
WDYT ?

@michaelrambeau
Hello @Okazari thank you for the feedback.
So this "Miscellaneous" category would cover the projects that are not among the 25 top projects overall, neither among one leaders of one of the categories.

To satisfy your curiosity, isn't it simpler to check the "Trending / 12 months" pages, from Best of JavaScript application?
This way you can pick any category (or "tag") and check the 2017 leaders.

E.g. https://bestof.js.org/tags/bot/trending/last-12-months

@Okazari
@michaelrambeau You got a point here. But i'm also lazy and would love to avoid having to check all the categories by hand. (Well i could do it, but what i want to say is that it would simpler to provide it ;) )

Btw, if you're ok with the idea, i can make a pull request.

@michaelrambeau
@Okazari Just to understand how it would look like, how would you pick up the projects to be mentioned in the "Miscellaneous" category?
Targeting some categories and picking the project number one last year?

Please, add your name to the following checklist in order to avoid conflict.

• @melancholy14 i18n/md/colloections/2020/ko/categories/all.md
• @melancholy14 i18n/md/colloections/2020/ko/categories/angular.md
• i18n/md/colloections/2020/ko/categories/build.md
• i18n/md/colloections/2020/ko/categories/cssframework.md
• @melancholy14 i18n/md/colloections/2020/ko/categories/framework.md
• @melancholy14 i18n/md/colloections/2020/ko/categories/nodejs-framework.md
• @melancholy14 i18n/md/colloections/2020/ko/categories/react.md
• @melancholy14 i18n/md/colloections/2020/ko/categories/vue.md
• @melancholy14 i18n/md/colloections/2020/ko/guests/atinux.md
• @melancholy14 i18n/md/colloections/2020/ko/guests/bblackwo.md
• @melancholy14 i18n/md/colloections/2020/ko/guests/leerob.md
• @melancholy14 i18n/md/colloections/2020/ko/guests/slorber.md
• @melancholy14 i18n/md/colloections/2020/ko/conclusion.md
• @melancholy14 i18n/md/colloections/2020/ko/introduction.md
• @melancholy14 i18n/messages/2020/ko.json
• @melancholy14 i18n/messages/common/ko.json

Should we have Animation libraries as a separate category? https://bestof.js.org/tags/animation/

I apologize for raising this as an issue, but I couldn't find any discussion section or Discord community for this project. I hope my message finds you well. I have a quick question regarding the project - how is the /data updated?

Thank you for creating this project, and I appreciate any help you can provide.

I know there’s the 2016 version, but I mean being able to compare in the same place if the project is accelerating or decelerating

For example Feathers went from +4.1k stars in 2016 to +2.9k in 2017, so it would seem to indicate that it’s losing speed while of course other projects are growing faster and faster. That could be interesting to highlight somehow.

For example instead of grey bars, we could have green bars when it’s a positive trend and red bars when it’s negative and show the increase on hover maybe, or next to the number of stars

This issue tracks the steps related to the preparation of 2018 JavaScript Rising Stars.

Changes

Compared to 2017:

• One more category: the Angular ecosystem, see issue #32
• "Misc" category was removed because there is a "SHOW MORE" added on "Most Popular Projects Overall", see issue #7
• A menu to navigate between the years (2016 - 2017 - 2018) has been added
• Next.js and Nuxt projects are also considerered as "Static Site Generators", see michaelrambeau/bestofjs#207 (comment)

Translations

• The Spanish version has been made by @jvalen
• The Chinese version has been made by @seognil #35

Images

To be included in README.md file (don't delete!)

Great job with the 2019 rising stars summary -- it looks awesome (I love the integrated bar chart in the background of each category!

I maintain Storybook, which is one of the top projects overall (just below the fold) but since apparently it's in its own category, it's effectively buried.

Would it be possible to include storybook in the testing category, as it was for StateOfJS? I would also be very happy if it was considered in the react/vue/angular ecosystems, since it's the top component workshop (and documentation system!) for all three frameworks. 😄

The user experience on mobile is not great:

• the navigation to menu to switch between years is crowded
• the language drop-down menu seems to be broken
• Lighthouse metrics should be improved

Among the points for fix:

Avoid an excessive DOM size 7,772 elements

Route (pages)                              Size     First Load JS
┌   /_app                                  0 B            73.6 kB
├ ● /[year]/[language] (49952 ms)          58.7 kB         132 kB
├   └ css/c686c22591dbfa2e.css             254 B
├   ├ /2017/zh (7032 ms)
├   ├ /2016/en (6400 ms)
├   ├ /2017/ja (6143 ms)
├   ├ /2017/en (4470 ms)
├   ├ /2017/fr (3101 ms)
├   ├ /2016/ja (3038 ms)
├   ├ /2016/zh (3028 ms)
├   └ [+22 more paths] (avg 761 ms)
├ λ /[year]/[language]/design              1.63 kB        75.3 kB
├   └ css/498c7c84c4a76fb3.css             171 B
└ ○ /404                                   183 B          73.8 kB
+ First Load JS shared by all              76.6 kB
  ├ chunks/framework-581f102fc68ef277.js   45.4 kB
  ├ chunks/main-c54db12ec8301afa.js        27.1 kB
  ├ chunks/pages/_app-aa8690e3a3d18c5d.js  351 B
  ├ chunks/webpack-59c5c889f52620d6.js     819 B
  └ css/0b8fc5dbefb69b6f.css               2.97 kB

File sizes in .next/server/pages/2022 folder:

• 452K en.html
• 104K en.json

On Twitter, Brent Vatne (GitHub profile) told us that we should include 2 projects among the "React Ecosystem" projects:

• https://github.com/react-community/create-react-native-app
• https://github.com/react-navigation/react-navigation

In Best of JS, these 2 projects are tagged under React Native tag and not under React, that's why they don't show up in Rising Stars.

So we have 2 options.

Option A

Include also React Native projects in the "React ecosystem" category

Doing this, and exluding both React and React Native projects, the TOP 10 would change like this:

No more React Boilerplate and Recompose, that are mentioned in the comments.

That's why we could show more projects maybe, 15 instead of 10, for example.

Option B

Add a React Native category... but we would have to add comments.

This issue tracks the different steps of the building process of "JavaScript Rising Stars 2017".

The concept is the same as last year: analyzing the trends over the last 12 months, showing both raw numbers (how many stars were added on GitHub in 2017) and providing interesting explanations

We will try to repeat the success of https://risingstars2016.js.org/. (see the story here: michaelrambeau/risingstars2016#1)

Hey I love your rising stars page! Really useful to keep on top of popular tech.

I was wondering if you could add an Angular Ecosystem section. I see you have Vue and React. Adding Angular to the list would be great!

We need a summary of the Vue.js landscape in 2019.

I'm not an export but maybe someone like Sébastin Chopin @Atinux could help us?

Especially given the fact that Nuxt is in the TOP 5 of the Vue.js projects!

Temporary URL: https://2019--risingstars.netlify.com/2019/en/

See: http://risingstars_demo.frankxu.me/ by @frankyxhl

Feedback/Questions:

• We need to restrict it to the list of projects that are actually featured in the Rising Stars page.
• Can we incorporate the project icons somehow? If so can we detect their colors?
• Will the diagram be responsive? Will it work on mobile?
• How heavy will it be? Do we need to load D3 or can we just use a static export?
• How do we pick colors?

Weex doesn't show in current page?

Should add it into projects.json:
https://img.alicdn.com/tps/TB1zBLaPXXXXXXeXXXXXXXXXXXX-121-59.svg

hey michael! was thinking of doing additional analysis on this data but need the daily data.. i couldnt find it here. Is it open for public view? thank you!

I think we should harmonize the layout of each section. How about showing 10 items to begin with, and having a "show more…" link to show the next 10?

Google PageSpeed Test result is bad:

• 40 / 100 on Mobile
• 53 / 100 on Mobile

I will see how we can improve that by decreasing the number of HTTP requests maybe, now we load a lot of images (164 requests!), because all avatars are loaded 2 times, once for the Table of Content, the second time inside the table rows.

These are all the missing images I found. You can see it's showing the alt text on the ToC.

• Vue Element Admin
• Hyperapp
• Omi
• Next.Js
• React Native
• Docz
• Bulma
• Formik
• Hyperapp
• Mithril
• Sails
• Loopback
• Docsarus

I thought it might be useful to have a list of roundup/trends/etc. Maybe write a meta-analysis?

https://hackernoon.com/the-top-javascript-trends-to-watch-in-2018-a8437dd94425

Hi Michael,

I found the images are squashed viewing the weekly issue on my phone.

Maybe on mobile, you could remove the "homepage" link and make the title clickable instead (like you do in the email)? That would give more room for the image.

Hey, with 4.2k starts elm-compiler should be on the compilers list, right after Flow and before Reason

Hey, I love what you guys are doing with bestofjs :).

If you have some time, the following branding would be even better, I couldn't find where it's hosted to make a pull request, so here is it :)

-name: Material UI
-logo: https://bestofjs.org/logos/material-ui.svg
+name: Material-UI
+logo: https://avatars2.githubusercontent.com/u/33663932?s=150&v=2019

Add direct links to GitHub repos for each library.

This is more of a personal preference, but I don't think we should name components index.js, because it makes it harder to quickly switch to them in your text editor or even do a site-wide search.

Also we should keep naming consistent, for example ProjectTableView is defined as ProjectTableView but imported as ProjectTable, again making it hard to understand the code.

I feel like we should also be able to see the total number of stars. For example, it would let us see how far Vue still is from React, and estimate when it will catch up.

Stories of the year

Collecting material from javascriptweekly.com issues in order to write the Stories of the Year

Facebook open-source license drama

Oct 2016 305

A Lawyer Analyzes Facebook's React.js License
Robert Pierce concludes React is not ‘open source.’ This spawned a large Hacker News discussion.

August 2017 349

Facebook Explains React's License
Facebook reacts to Apache’s recent critique of React’s ‘BSD + Parents’ license by explaining how it helps them contribute to open source.

graphql/graphql-spec#351

https://medium.com/@reverdev/why-we-moved-from-angular-2-to-vue-js-and-why-we-didnt-choose-react-ef807d9f4163

Sept 2017 354

Facebook Relicensing React, Jest, Flow, and Immutable.js
Recently, there have been some issues involving patent-related features, but Facebook is now moving some of its projects to a standard MIT license.

WebAssembly

webpack Awarded $125,000 By Mozilla news
To implement first-class support for WebAssembly.

An Abridged Cartoon Introduction To WebAssembly
Lin Clark explains what exactly WebAssembly is, and what makes it fast.

WebAssembly Will Let You Run High-Perf Apps in Your Browser story
A neat high level overview of WebAssembly.

WebAssembly Will Finally Let You Run High-Performance Applications in Your Browser
Online applications could work as smoothly as the programs you install on your machine

Reason

What is ReasonML?

This blog post gives a brief high-level explanation of Facebook’s new programming language, ReasonML.

Node.js evolution

• node.js now supports all major features from ES6
• async/await makes asynchronous programming far much easier (Nested Promise Callback Functions > Promise chains > Async Await)
• Next step: supporting import and export?

While they're a crucial part of most applications, database libraries (ORMS, query builders, ...) don't get much attention in the Node.js ecosystem. I would suggest to maybe introduce a new category that would include these libraries and also solve the issue that Prisma is mis-categorized in the "GraphQL"-category.

Note that Prisma 1 indeed used to be a "GraphQL generator" but Prisma 2 (now 3) is purely a DB access library.

Capturing some of the feedback / ideas for the 2021 Rising Stars.

General

• More connection with Best of JS: after the TOP 10 a link “View the category on Best of JS” to show people the full list of projects?
• More interactivity for each section to let users compare data for each year without having to leave the page in order to go to an other year

Categories

• A monorepo category?
• A runtime category?
• Maybe a more generic "Tooling" category to include build tools, monorepo, etc
• Maybe we could link to Best of JS for the additional categories not covered?

Doesn't look very good… Can we use a larger size (1.5x or 2x display size) or is that the only size available from GitHub? If we can't use larger images we should reduce the dimensions of the image when displayed.

Add your name to following lines before starting translation to avoid conflict.

コンフリクトしないように翻訳開始前に↓のリストに名前を書いてからはじめましょう。

Edit "ja.md" in each directory such as "i18n/2017/introduction/ja.md".
When you translated, and git pushed, check the corresponding checkbox.

• @azukiwasher i18n/2017/introduction
• @azukiwasher i18n/2017/conclusion: 'おわりに'
• @azukiwasher i18n/2017/categories/all: '2017年人気プロジェクトランキング'
• @azukiwasher i18n/2017/categories/framework: 'フロントエンドフレームワーク'
• @azukiwasher i18n/2017/categories/nodejsframework: 'Node.jsフレームワーク'
• @meltedice i18n/2017/categories/react: 'Reactボイラープレート'
• @meltedice i18n/2017/categories/vue: 'Vue Ecosystem'
• @azukiwasher i18n/2017/categories/mobile: 'モバイル'
• @azukiwasher i18n/2017/categories/compiler: 'コンパイラ'
• @azukiwasher i18n/2017/categories/build: 'ビルドツール'
• @meltedice i18n/2017/categories/testframework: 'テスティングフレームワーク'
• @azukiwasher i18n/2017/categories/ide: '統合開発環境（IDE）'
• @azukiwasher i18n/2017/categories/ssg: '静的サイトジェネレータ'
• @azukiwasher i18n/2017/categories/css-in-js: 'CSS in JavaScript'
• @azukiwasher i18n/2017/categories/graphql: 'GraphQL'
• @azukiwasher i18n/2017/guests/evan: 'スペシャルゲスト'
• @azukiwasher i18n/2017/categories/misc: '番外編'
• @azukiwasher i18n/2017/common

Is that on purpose? Did we decide not to have the same projects appear in multiple categories?

This issue tracks the progress of the 2020 edition of the Rising Stars.

No change in the concept but the project is now built using Next.js instead of Gatsby.

The reason? I was contacted by Guillermo Rauch last year to host the Rising Stars on Zeit Now platform (that became Vercel later). So I thought it could a good occasion to use Next.js since I've heard a lot of good things about it!

The first iteration is available in the branch called next.

https://javascript-risingstars.vercel.app/

Screenshot to be linked in the README.md: