HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vuejs
vue
TypeScript2015–2025
vuejs / vue

vue

This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core

49Distinct people
54Mentions
2Explicit recommenders
212.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I also am. I love the simplicity of vue api, but I hate vue-cli, webpack(it is good because it's configurable and extensible, but it's overwhelmingly complex, all the output…

rhengles used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year54 dated mentions

Observed mentions: 2015-10-21 15:37:41 UTC to 2025-05-27 19:13:46 UTC.

051015202015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 18 mentions; 6 submissions, 12 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 10 mentions; 5 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC18612
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC1055
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1129
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

10 sources
Meaningful contribution in what way? This is Vue's contribution graph sorted by addition: https://github.com/vuejs/vue/graphs/contributors?from=2016-0... The #2 person contributes only about 1% compared to the #1 person. Compare to React's same graph: https://github.com/facebook/react/graphs/contributors?from=2... The #2 person is at about 50% of the #1 person. Compare to Ember's same graph: https://github.com/emberjs/ember.js/graphs/contributors?from... The #2 person is at 75% of the #1 person.
In Will Vue.js become a giant like Angular or React?
> Two way data binding [...] is a very good option for small applications or POC. But for very complex UI you should consider using one way data binding and explicit state updates/mutations. I don't agree with this. Two-way data binding is a powerful tool that can make composing components very effective when used correctly in any size application. If you have a number of custom generic input components (sliders, color pickers, value inputs with popup sliders, etc...). Being able to compose them into a custom ui just by binding with v-model is remarkably efficient for the developer. Having said that this is only good when you compose dumb or generic inputs. Once you are in a component that is a bit more high level then yes, absolutely Vuex is the right way to manage your state. The problem is that to bind components with v-model you have
Read the rest
to deep-clone your data, and watch it. This is far from ideal. I raised an issue related to this because I think Vue is kind of missing something here. https://github.com/vuejs/vue/issues/4373
In VueJS – Two way data binding and state management with Vuex and strict mode

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.