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

Web Development
Explore on GitHubRead Hacker News discussions
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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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

54 sources
moritzwarhier·May 27, 2025
Lodash also has "isPlainObject". Not sure if that's as performant as using Array.isArray or even simpler trickery (see below), but it seems that this fixes it. "isObject" is just not well-defined for other cases that might be interesting, in my opinion. Not just "null" or arrays. Functions can have properties (although they don't have the object prototype or primitive type). Class instances behave differently compared to plain objects when used with libraries or other code that inspects the shape or prototype of objects, or wants to serialize them to JSON. If you deal with unknown foreign values that are expected to be a JSON-serializable value, you could go with something like isObject = (o) => !!o && typeof o === "object" && !Array.isArray(o) But it does not deal with all the non-JSON objects, e.g. Map or other class instances that a
Read the rest
re not even JSON-serializable by default. When data comes from parsing unknown JSON, the check above should be enough. In other cases, the program should already know what is being passed into a function. No matter if through discipline or with the aid of an additional type syntax. For library code that needs to reflect on unknown data at runtime, I think it's worth looking at Vue2's hilarious solution, probably a very good and performant choice, no matter how icky it might look: https://github.com/vuejs/vue/blob/547a64e9b93d24ca5927f653710b5734fa909673/src/uti… Since the string representations of built-ins have long ago become part of the spec, it seems that there is no real issue with this!
In Show HN: SuperUtilsPlus – A Modern Alternative to Lodash
phil294·May 4, 2023
Angular is as little innovative for web frameworks as Firefox-ESR is for browsers. It merely keeps copying features from other frameworks - just many years later. It is a chronically outdated framework that always struggles to keep up with its competitors. It would be ok if those were deliberate design decisions, but if the features get copied some day anyway, what is the point? Why not do it the right way from the start? For example, this update brings us computed properties, an essential feature for any complex performant web application that was made popular by Vue.js 10 years ago [1]. And now in 2023 we get it in Angular, essentially a confirmation by its devs that its lack had always been a design error. I also cannot understand the "mature" argument. For example, it took five years for documentation on the integral `<ng-content>` to
Read the rest
arrive [2]. This is something I'd expect from the side project of a lone programmer, not an enterprise-level framework. The only upsides of Angular are its "batteries included" approach and the (debatable) default of RXJS, while the downsides are plenty (see other comments). [1] https://github.com/vuejs/vue/tree/218557cdec830a629252f4a9e2... [2] https://github.com/angular/angular/issues/17983
In Angular v16
archibaldJ·Jan 20, 2021
> So far there isn't much opensource written in China There are lots of opensource written in China. I think you have mistaken my stance on this. The Chinese open-source microcosmos are pretty cool. It's just that I have yet seen anything reactjs-great[1], let alone linux-great. Here are some github repos by the big players: Ant - https://github.com/ant-design TaroJS - https://github.com/NervJS Tencent - https://github.com/Tencent Baidu - https://github.com/PaddlePaddle ... There are also many pretty nice libraries written and maintained independently by devs (or small startups) in China. dayjs - https://github.com/iamkun/dayjs GPT2 in Chinese - https://github.com/Morizeyao/GPT2-Chinese Wechaty - https://github.com/wechaty vercel ssg - https://github.com/shuding/nextra ... [1]: For example, vuejs (https://github.com/vuejs/vue) is closed t
Read the rest
o being reactjs-great. It is by Evan You who is now New Jersey-based (though looks like he's quite involved in the Chinese tech scene which is pretty intriguing)
In China wants to build an open source ecosystem to rival GitHub
rhengles·Mar 20, 2020
> One of the reasons they picked Vue is because (...) it allows you to do so without a build step I think it's great that Vue is capable without a build step; however, this implies one restriction, which is that you must have all the components loaded before the application starts. And Async components don't help here because you would have to mantain a list of components names, which without a build step become cumbersome. I would like that my proposal for lazy loading components (https://github.com/vuejs/vue/pull/8807) would be accepted, then we would have the ability to load components on demand without a build step.
In RFC: Adopt a modern JavaScript framework for use with MediaWiki
rhengles·Jun 25, 2019Recommendation phrase
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 formats are a pain to debug, I have never seen sourcemaps work in chrome developer tools) and single file components. That led me to create my own architecture to scaffold vue apps, which Evan You seems to hate. https://github.com/vuejs/vue/issues/8106 In this comment, I showcased some production apps running with this: https://github.com/vuejs/vue/issues/8106#issuecomment-386064... https://github.com/vuejs/vue/pull/8807 I have improved this architecture even further in new apps, but I hadn't time yet to update the "vue-generator" boilerplate.
In Vue: We no longer have any plan of deprecating the Object API
exogen·Dec 17, 2018
I see you have never had to implement Promises in userland. :) setImmediate is one of the more popular polyfills in fact, all the workarounds you mentioned either have downsides or are ugly hacks. It's useful to anything that has a scheduler. Like Vue for example. Maybe someone should tell Evan You that it doesn't make sense to need setImmediate? https://github.com/vuejs/vue/blob/b111de486b1bdc747fe0f5795f... Check the download counts: https://www.npmjs.com/package/setimmediate https://www.npmjs.com/package/next-tick https://www.npmjs.com/package/set-immediate-shim https://www.npmjs.com/package/core-js#setimmediate
In Browsers
rhengles·Jul 17, 2018
Evan, if you are reading, I would like to say that I also fell in love with Vue, but I am frustrated that my feature request ( https://github.com/vuejs/vue/issues/8106#issuecomment-385367... ) was a little too quickly shot down, without much discussion or understanding. I understand that not every proposal can be accepted, but I think that the merit of the change wasn't even considered. I specifically designed the change to change as little as possible, and have as much power as possible. I think that specifically in the case of Vue, this hurts more because of the philosophy highlighted in the article- to not stand in the way of experienced developers who know what they're doing. (Edit: oh no, please don't come with the downvote train. This is a real issue, when you have something that solves 99% of your problems but you can't get it to 1
Read the rest
00%.)
In Love letter to Vue

Showing the 15 most recent of 54 sources. Enable JavaScript to search and browse every indexed mention.

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.