r/javascript • • Jun 28 '18

The exact same app - 1 version made with React, Redux, and React-Router The other made with Vue, Vuex, Vue-Router. Good if you want to see both worlds. User Auth with JWT, note CRUD actions, Koa (Node) backend. MIT license.

https://johndatserakis.github.io/koa-react-notes-web/
459 Upvotes

98 comments sorted by

38

u/adstwlearn Jun 28 '18 edited Sep 05 '18

Edit: I've written a blog post on this experience - you can read it on vuejsdevelopers.com.

(Use demousername and demopassword to login without creating an account)

I've been using Vue for about 2 years. Developer for about 8. When I first started to learn Vue I decided I would learn it out in the "open" by opensourcing a simple notes app that had fuller features like user auth using JWT and full CRUD note actions. This was partnered with a backend node API built using Koa.

Recently, even though I really dig Vue, I'm interested in React and decided to jump right into it - and I figured what better way then to recreate the the notes app.

In the process I've learned all about React, Redux, React-Router, Styled-Components, the render function, Higher Order Components - it's been fun.

Happy to answer any questions.

Link to the React version demo | Link to the React version github

Link to the Vue version demo | Link to the Vue version github

Link to the backend Koa github

10

u/Morphray Jun 28 '18

Do you have pros and cons of each?

25

u/adstwlearn Jun 28 '18 edited Jun 28 '18

See my response below. Basically I dig React - but I fuck with Vue heavy due to having just enough magic to be super helpful, but not so much that I feel separated from the code.

5

u/1-800-BICYCLE Jun 28 '18 edited Jul 05 '19

1fb6518db439

14

u/[deleted] Jun 28 '18

Vue's magic isn't really DOM-related. It's more stuff like having e.g. v-if attributes instead of leveraging raw JS (for better or for worse) in React like condition && <Comp />. If you're doing React correctly you should never go near the DOM.

10

u/1-800-BICYCLE Jun 28 '18 edited Jul 05 '19

11247258704d3

4

u/Peechez Jun 29 '18

In my time using Vue, the only time I've manipulated the real DOM was to pause/play a video. It really isn't that common

1

u/youlleatitandlikeit Jun 28 '18 edited Jun 28 '18

Is there a reason that the two different apps have two different APIs? Seems like you could have just one API that served both the Vue and React front ends.

EDIT: Never mind, looks like they both use the one called koa-vue-notes-api?

6

u/adstwlearn Jun 28 '18

Yup! They're both using the exact same backend - at the same time ha. The code for the backend is here: https://github.com/johndatserakis/koa-vue-notes-api - that's open-source as well and using Koa on Node.

1

u/youlleatitandlikeit Jun 28 '18 edited Jun 28 '18

Follow up: any idea why it appears to be using old-style hash history locations?

Oh I see you set it up that way here. According to the docs it looks like BrowserRouter is only supported if you also can handle the URL on the server side. I assumed that the application could intercept it. Huh.

4

u/adstwlearn Jun 28 '18

Yea usually I do that by having nginx or apache serve the index.html at all times - works great. But the thing is that this is served on GitHub pages where you don't have access to the server - so I opted for the hash version so it would work with no problems on there.

13

u/tomcam Jun 28 '18

This Rosetta Stone approach makes it one of my favorite posts ever. Thank you so much.

5

u/adstwlearn Jun 28 '18

Thanks for checking it out - hope it can help

20

u/burge_is Jun 28 '18

Do you have a clear winner in mind between the two?

It is super vague of a question but I imagine a lot of folks would be interested to hear a kind of quick take on what you view as the more pleasant (or unpleasant) parts of each development experience, especially in relation to one another.

What sorts of things from each workflow do you miss when working in the other?

54

u/adstwlearn Jun 28 '18 edited Jun 28 '18

Great question. For me, it's Vue.

All in all - I did like React. Not too hard to pick up. It's complete, and has a great community. The thing is, it seems like there's less batteries installed. That can be a plus at first, but after you sorta get the idea of how things work, it seems like you're just writing more code then needed.

Like with React-Router and how, if a component was not a direct descendant of a Switch statement main route definition, then it didn't have access to the history prop - and I had to wrap it with the withRouter HOC. That was just a bit funny - although I do like how some components are truly dumb vs smart - I guess that's the intent. It's just a bit different from having the $router always available to use through this.$router in Vue. Small things like that stood out.

The strangest thing for me in React was the render function. In Vue it's just so easy to loop over data and spit out elements or show/hide data based on state/store variables - in React it felt pretty strange to have to create my notes loop outside of the render.

In Vue, if you want to show or hide something - just use <div v-if="myVariable">Lorem...</div> and it'll be based of your myVariable truthiness. In React it seems like you have to do:

{this.state.myVariable &&
  <div>Lorem...</div>
}

It's a little more verbose, and doesn't support that instant-helper looping that Vue can manage. But of course, after I familiarized myself with how to do those normal little things, it didn't seem too odd. It's like, ok, whatever - that's just how you do that.

One other thing - the redux and react dev tools are definitely not as nice as the Vue tools - from the style, to having to open a huge tree of elements just to see a component's state - it made it a bit tough to get a view of my app's variables. I may be missing something here though or using a version that isn't the current community standard.

I definitely like React, and I do feel it was important to spend a solid month with it to learn its intricacies, but I do think I'll be using my Vue setup going forward for most things. It's less code and a simpler coding experience with helpers that make sense and are just magical enough that they're helpful, but not too magical that I lose track of what's actually going on.

16

u/Capaj Jun 28 '18

Like with React-Router

I dislike this about react-router too. Way too verbose. Version 4 is better than previous ones, but still too lame. @reach/router now that's a router I love! It makes routing in react easy and fun. Too bad it doesn't support hash history.

1

u/adstwlearn Jun 28 '18

@reach/router

Hmm I'll have to check that out.

0

u/[deleted] Jun 28 '18

[deleted]

14

u/spooky___ghost Jun 28 '18

An important point you're missing is that any component that is receiving route information as props will be re-rendered anytime the route changes. On top of the other points mentioned above, opting in to receiving routing props is 100% the correct decision.

In real applications only very few top-level components require any route state. If child components require it they can opt in or you can pass it down through the prop chain. React is all about giving control to the developer you do not want anything to be automatic or implicit.

10

u/[deleted] Jun 28 '18

I think this is exactly the main difference between React and VueJS. Vue requires you to be comfortable with magic and tbf that magic makes 90% of use cases really easy to spin up and develop.

React on the other hand has a small surface area.
It really is basically (state, props) => view.

It's essentially functions all the way down. With React you know exactly when and why a component will re-render at the cost of maybe having to write more code (personally I think it's a small price to pay).

If you're building a few pages and forms you should probably go with Vue, you'll love it and it'll really speed up your development.

If you're building a complex desktop grade application React gives you more power to realize that and the explicitness is a godsend for maintainability.

7

u/[deleted] Jun 28 '18

Why not? I don't want routing available in components that don't need to know about routing.

This lets me be explicit about what I pass in. Why should my say Text component need to know what the current route is or have the ability to change it?

1

u/[deleted] Jun 28 '18

Yeah I agree. For being the defacto rooting library for React, it makes some mind bogglingly strange decisions. Is there another routing library that you prefer?

1

u/[deleted] Jun 28 '18

What are some of the decisions you find strange?

2

u/adstwlearn Jun 29 '18 edited Jun 29 '18

I'll chime in - one more thing I thought was sorta not nice was that there is no more query parameter support in v4 - so I had to download qs (I think it was called) to parse query parameters from the url. Wasn't too happy about that, although not the biggest deal.

2

u/[deleted] Jun 29 '18

Ah yeah I can get behind that. I'm always torn on things like that.

Like I get that there's a perfectly good package out there to do it and I get the argument that different users have different needs but damn it query params are part of a route!

1

u/NoInkling Jun 29 '18

The issue with query strings is that there's no standardised way to parse arrays and nested structures. There are at least 3 syntaxes that see common use, and each parsing library usually only supports one of them.

So react router had to make the tradeoff between convenience and staying unopinionated, and chose the latter, leaving it up to the user to pick their library of choice.

For future reference, there is now a built-in web API URLSearchParams that can parse query strings. It only has basic array support (retrieved via .getAll()), but it can work for simple use cases.

const queryParams = new URLSearchParams(location.search)

6

u/imatworkyo Jun 28 '18

I appreciate this run down and overall agree. But its interesting you seem to still be leaning towards React

- to me, we share the same opinions; although I am a tad harsher on React ( there are just so many special idioms and complexity compounds quickly on larger projects ). I just find it interesting that you seem to land on a different ultimate conclusion.

To me Vue is the way forward, its simplicity and ease of cognitive overhead is refreshing while supplying most of, if not all of the benefits of React

3

u/adstwlearn Jun 28 '18 edited Jun 28 '18

Seems like we agree - maybe I wasn't clear in my comment. I will be using Vue going forward for most things! (Will probably do a few smaller things in React to stay sharp at this point)

4

u/Charuru Jun 29 '18

Did you read it wrong? His preference was for vue.

3

u/imatworkyo Jun 29 '18

probably did

4

u/[deleted] Jun 28 '18

What are the special react idioms?

To me React has less "React" stuff than Vue does "Vue" stuff.

5

u/jsyoda Jun 28 '18

Vue has more special idioms than React imo - Vue has its own dsl in html - can you explain what you mean here?

I think where React shines compared to Vue is when an app becomes more complex:

When a piece of state updates in Vue, you set its new value. Is another piece of state being updated here at the same time by listening to this value? You don't immediately know and need to look around - tracking the state changes can be difficult.

When a piece of state updates in React, any other state changes that occur at the same time are immediately obvious.

2

u/jkoudys Jun 29 '18

Does "less code" really imply a "simpler coding experience", though? As a 3rd-party reading your code, I look at something simple like your App.vue, and look at how many modules are implied to have loaded without actually specifying its source. The <footer-main> for example, requires that your router.js is loaded, which registers a Vue.component (essentially a global) so footer-main is your Footer.vue. Not only is it harder to reason about, but it limits us if we want to code-split the chunk too.

If you're using direct imports, every missing one shows up as a big squiggly red line from static-analysis in my editor long before runtime. Every non-trivially small component can be included via an import(), so it only gets its chunk loaded when I decide it's needed.

There's a lot more that forgoing pure ecma for a micro language hinders you for too. Dead-code elimination is basically impossible, both because Vue.component and router are essentially globals, and because so much of the control logic (e.g. v-if) is in microlanguage. There's the complexity of needing to learn, write, and reason in multiple languages at once (both harder to build and reason about -- with React and emotion, I don't need a single line of CSS, or to write any HTML beyond the tiny boilerplate react-create-app makes).

Don't think I'm being too critical - super happy you wrote this and released it to everyone. I do think a lot of your problems with react are based more in familiarity with vue, and React not being enough like vue isn't really a flaw. Some of your criticisms of individual libs (especially router) are pretty spot on, but you're also not following some basic patterns that React devs (especially the FP-loving ones) routinely use. e.g. out of array methods map, reduce, filter, find, Array.from, [... ], etc., I find only a single Array#map, which is pretty unusual for a React app. React's all about passing in the same collection as a prop to different components, and rendering them differently, e.g. a collection of restaurants could be mapped to a bunch of pins on a <GoogleMap> in one place, a text list in your <Itinerary> somewhere else, Vegan options: {restaurants.filter(({ cuisine }) => cuisine === vegan).length} in another component, etc.

2

u/adstwlearn Jun 29 '18

Upvoted. I don't think you're being too critical. It's just one of those things where this is a full example, so there's a lot of moving parts. I would argue that things like <footer-main> all follow the same exact pattern, so while it may seem strange at first, you'll pick up the structure right away.

Regardless - there's definitely something to be said about how you have to explicitly do certain things in React - like adding routing support to the footer if you wanted to push from there. I can definitely see the argument that it keeps things more focused and compartmentalized.

5

u/TheMr_ Jun 28 '18 edited Jun 28 '18

In regard to the return function, I see it as more separation of concerns. JSX is already being intermingled within each component alongside the normal JavaScript. For me, I'd say it helps keep the UI and Data separated more. What I found when learning React was that it tries to rely heavily on vanilla js where it can. Learning React taught me a lot more what could be done with vanilla js and has improved my overall understanding of just javascript as a whole.

And with that, it's fairly easy to loop over data within React just with plain javascript. Simply map over an array and pass in a component or element to be returned.

let state = {
    array: [1,2,3,4,5]
}

render(){
    return(
         <React.fragment>
             {this.state.array.map(number=><span>{number}</span>)}
         </React.fragment>
)}

Which will be rendered as the following into its parent container

<span>1</span>
<span>2</span>
<span>3</span>
<span>4</span>
<span>5</span>

You can also use the filter and map functions in conjunction to check whether an item should be rendered at all.

3

u/ImOutOfThisWorld Jun 28 '18

you forgot the "{}" in:

<React.fragment>
    {this.state.array.map(number=><span>{number}</span>)}
</React.fragment>

2

u/TheMr_ Jun 28 '18

Can't believe I forgot that. Thanks, I've edited my reply

3

u/crazyfreak316 Jun 28 '18

Learning React taught me a lot more what could be done with vanilla js and has improved my overall understanding of just javascript as a whole.

I can completely relate.

2

u/ihsw Jun 28 '18

<React.fragment> elements can be replaced with empty-bracket elements.

Eg:

<>
    {this.state.array.map(number=><span>{number}</span>)}
</>

And, furthermore, you can return bare arrays of rendered elements, so even that is unnecessary.

render() {
    return this.state.array.map(number=><span>{number}</span>);
}

1

u/NoInkling Jun 29 '18 edited Jun 29 '18

<React.fragment> elements can be replaced with empty-bracket elements.

Only with Babel 7, which is still in beta (and maybe Typescript?).

And, furthermore, you can return bare arrays of rendered elements, so even that is unnecessary.

You'll get a warning about missing keys though (which means it's less optimized).

Edit: actually the first example will also have the key issue, so you're right, there's no advantage to using the fragment in this case. Any time you use an array you should add keys though.

1

u/ihsw Jun 28 '18

<React.fragment> elements can be replaced with empty-bracket elements.

Eg:

<>
    {this.state.array.map(number=><span>{number}</span>)}
</>

1

u/Morphray Jun 30 '18

You forgot semicolons at the end of your statements. ;)

12

u/[deleted] Jun 28 '18 edited Jun 29 '18

[removed] — view removed comment

8

u/sonofamonster Jun 28 '18

It has the best name though. It sounds like it’s the router that you’re supposed to use.

6

u/equake Jun 28 '18

Are there good alternatives?

2

u/[deleted] Jun 28 '18

What about it?

1

u/[deleted] Jun 29 '18

[removed] — view removed comment

1

u/adstwlearn Jun 29 '18

Oh ok, nice. But that's not reactive right? Or could I use this.state.boolean as the true value there to make it reactive?

-17

u/0987654231 Jun 28 '18

Do you have a clear winner in mind between the two?

well the vue version doesn't work so....

5

u/adstwlearn Jun 28 '18

Sorry 'bout that bug - the nav bar works now for mobile and you can login/signup no problem.

6

u/burge_is Jun 28 '18

That issue doesn't speak to his experience with the two frameworks.

Get outta here with that snarkiness.

-14

u/0987654231 Jun 28 '18

Actually that's exactly what it does. He tried something in two frameworks and had a poor result in one

5

u/burge_is Jun 28 '18

No he had a bug in one.

It's software, bugs are the norm.

There is nothing magical between the two that makes code 100% bug-free. Yes the way you work in a framework can introduce behaviors that are bug inducing but the idea that this single bug answers the question is laughable.

-9

u/0987654231 Jun 28 '18 edited Jun 28 '18

So just to be clear, he tried two things, and had more success in one compared to the other? I think that speaks to his experience. You can also see it took him >4x the commits to create the vue SPA, which again I think speaks to his experience.

No need to get upset,his experiences and my snarky comment don't make your favorite frameworks better or worse.

3

u/burge_is Jun 28 '18 edited Jun 28 '18

Hahaha I don't have a favorite in this mix.

I'm suggesting that he would have a better understanding of his experience, with the two, than you or I would and that is why I was asking him for it. Rather than declaring an answer for him based off metrics that paint an incomplete story.

Forgive me for being so terribly upset.

6

u/isakdev Jun 28 '18

Now benchmark them

1

u/adstwlearn Jun 29 '18

Ha yup - that would be a good idea.

7

u/klepra Jun 28 '18

I see you are using quite a modern style with backend (async, OOP, classes, testing).

I am primarly a Java programmer and doing a bit of node on my own - I can write Express based REST backends, but it is pretty basic. Any suggestions how to pick up this things (async synthax, classes with js, backend) or just keep coding in Node?

10

u/adstwlearn Jun 28 '18 edited Jun 30 '18

Thank you for checking it out.

Well I think the biggest thing for me when learning is to make little/medium sized projects that have a specific scope.

As you move through building an app, you're forced to deal with very real issues that really teach you so much. For example, really ironing out the rather complicated JWT User Auth has been a great teacher. Really, the whole User Auth part, on all the apps, is such an important and large part that you're bound to see pretty much everything there - like a micro-ecosystem.

As far as async/await goes - it's something that I think scares people a bit - but people should actually be happy to see it because it allows you to be removed from the callback hell that exists with then promise handling and older plain callback handling.

So just keep coding - decide on a side-project you're interested in - and code the hell out of it like you're going to show it to Linus himself. I find myself feeling uncomfortable in my code all the time - that's how I know I'm making progress.

Peak at the koa backend when you need help - I made it specifically to help those stuck on some of these concepts.

Edit: Also - I f'ing love Koa - so simple - it just gets out of the way. And with full async/await support - it's killer. The entire route is just a nice promise chain.

2

u/klepra Jun 29 '18

Thank you, good advise, I agree with doing small complete projects with specific scope.

I have quite the same approach actually; I made similar apps in different (back-end) technology - I've built Angular polling app with Java Spring Boot Backend and Node back-end, but Node version is pretty basic - no tests etc. Also some other logger like app. Pretty simple and not really polished yet, but I like the feeling of building a complete application, even if it is very simple - and you can add-on to it in the future.

I agree on jwt/auth part - I've recently started to implement it in my learning projects (both, Java and Node), although I am not using refresh/access tokens yet - only one. I will check out your approach with JWT. I guess once you understand how to implement user authentication in a specific technology you are starting to get pretty comfortable with it.

I guess I understand async/await but not quite used to it yet as I don't really work much with JavaScript directly, apart from checking out some videos/tutorials - as a Java dev I am pretty comfortable with Angular but I will dig into React more in the future and make some simple apps as I believe it will improve my JavaScript understanding. And also switch Express for Koa. My day-job is mostly maintaining legacy Java applications so I have to keep myself up to date by learning on my own.

2

u/Donutttt Jun 28 '18

Do you do any front end work? Often you can do more async stuff on the front end and the apis are quite similar.

1

u/klepra Jun 29 '18

Mostly Angular as far as front-end goes, but subscribe model with observables is more often used then promises.

1

u/Donutttt Jun 29 '18

Yeah angular is really heavily setup with observables, which don't seem to have taken off hugely with any other frameworks. Promises are fairly similar to be honest, but if you wanted to use them more, you may want to take a look at react or vue

2

u/honigbadger Jun 29 '18

Check out NestJS, Thank me later :)

1

u/klepra Jun 29 '18

Looks really good. Gotta find time for trying it out soon :)

3

u/harrymurkin Jun 28 '18

Why did you dodge angular 2+ ?

4

u/adstwlearn Jun 29 '18 edited Apr 18 '20

Haha I didn't dodge it - well, I guess I did. At the moment I don't have any plans to make an Angular version. Although I'd love to look through something similar just to see how it's setup. Evan was on the Angular team I believe - so there must be a few things that carry over.

1

u/harrymurkin Jun 29 '18

I was just wondering if it was because angularJS is no fun as compared to angular2 with CLI. I crammed react and angular 2 at the same time a few years back and found them to be very similar. Chose google over facebook rather than preferred syntax/stacks.

3

u/leftHandHacker Jun 29 '18

Why Google over Facebook? I don’t have any particular leaning either way, just wondering. I chose React over Angular 2, because I had a terrible time with AngularJS and saw that Angular 2 was essentially following in the wake of React. That led me to believe that developers in general (even at Google) saw React as a superior paradigm, and would therefore lead to more job opportunities since Angular would have to fight too hard to regain market share that they must have lost to React.

2

u/harrymurkin Jun 30 '18

I don't like facebook's disregard for privacy. Nothing to do with the code, but good point regarding angularJS market loss.

2

u/DonPhelippe Jun 29 '18

Thanks for that, a very good way to do some comparisons between frameworks, much better than the usual fanboi wars. Also like the fact that your app more or less is kinda complete. You don't mind if I take a good look at your code concerning your auth techniques, right?

2

u/adstwlearn Jun 29 '18

Of course - hope it helps.

3

u/[deleted] Jun 28 '18

I can't open the Vue ones menu when I tap. Chrome Mobile on Android

4

u/adstwlearn Jun 28 '18 edited Jun 28 '18

EDIT - This is fixed - nav works now on Vue version and you can login/signup no problem.

Darn, sorry about that. Must have broke that on a recent build. Will fix asap.

1

u/coolreader18 Jun 28 '18

Reddit automatically highlights links, you only have to do []() if you want to name the link.

1

u/Mabenue Jun 28 '18

Same

1

u/adstwlearn Jun 28 '18 edited Jun 28 '18

All set now - sorry about that bug.

1

u/1-800-BICYCLE Jun 28 '18 edited Jul 05 '19

18817b606385

1

u/Funcod Jun 29 '18

Iv read that storing the JWT token in the localStorage is less secure than using Secure cookies + CSRF.

1

u/adstwlearn Jun 29 '18

I hear you. I've read that whether you're storing JWT's in localStorage or in cookies you still have to keep an eye on security. Ways to do that are by setting a short expiry time on the JWT (it's set to about 15m here), and by encrypting the the JWT (it's encrypted with a key so if it's changed in any it's declined). And there's also nothing mission-critical in the JWT, just to be safe. Also of course the other routine things you do to keep things safe.

But I def hear you and it's important to keep an eye on these types of security issues.

1

u/EstebanVelour Jun 29 '18

What about adding TypeScript & storybook? I've found both kind of indispensable for larger projects.

2

u/adstwlearn Jun 29 '18

Def interested in both. Going to research them for sure.

1

u/annonn_ Jun 29 '18

OP I was going through your backend code and there a lot of bad practices with Koa routing. For example in your Routes files you declare your routes like this:

router.post('/api/v1/user/signup', async (ctx, next) => {
    await userActionController.signup(ctx)
})

when it can be set up like this:

router.post('/api/v1/user/signup', userActionController.signup)

Also instead applying the same middleware to 10 routes individually, you can apply blanket middlewares using 'router.use()'

And I'd also use route prefixes for common routes things like '/api/v1/' instead repeating yourself.

3

u/adstwlearn Jun 29 '18

Thanks for the feedback.

I'm not so sure about you example though - if you look at the first example on koa-router you see they have it like I have it.

That's not to say your way isn't better - but to say that they way I have it, the official example way, is bad practice - I think that's a bit too intense.

I'm about as smart as a bag of bricks though - so I could be doing the whole thing wrong haha.

Also instead applying the same middleware to 10 routes individually

Are you talking about the JWT middleware? That's only for protected routes - I'd like to keep that separate and only apply it when I'd like.

Thank you for the perspective!

-1

u/annonn_ Jun 29 '18 edited Jun 29 '18

First I thought you just made a simple mistake but your reply tells me you don't seem to understand basic JS like callback functions.

function callbackFunction(ctx) {
  //do something
}

// Bad
router((ctx) => {
    callbackFunction(ctx)
});

// Is exactly the same as above except is done in a single line instead of three
router(callbackFunction);

No offence but this is basic JS stuff. Maybe you should learn the language first before attempting to write educational code for other people?

8

u/adstwlearn Jun 29 '18 edited Jun 29 '18

My dude - I hear what you are saying. I know what your example is showing.

I'd like to have it like the official documentation has it. Does that mean I don't know how JavaScript works? I guess.

Thanks for the feedback. I can tell you know a lot about this, and although your tone is a bit off-putting, I'm still going to gather positive feedback from you reply. I wish you'd be more civil so I could actually ask questions and gather information from you.

Thanks again.

1

u/Ethesen Jul 06 '18 edited Jul 06 '18

The example you mentioned:

router.get('/', (ctx, next) => { 
    // ctx.router available 
});

Your code is the equivalent of:

const callback = (ctx, next) => { };
router.get('/', (ctx, next) => { 
    callback(ctx, next); 
});

Examples in the docs are written well. Your code isn't. It's redundant.

-2

u/ImpressiveHamster Jun 29 '18

No you're not hearing what I'm saying. You don't even seem to understand that there's difference between your Koa-router code and the example on koa-router github page. You're using 2 extra lines of code per route. If your app has a 100 routes, that's 200 extra line of code that shouldn't be there. This is completely unacceptable.

2

u/mayhempk1 Jun 29 '18

Well, that's awesome. Thanks for releasing this!

2

u/leftHandHacker Jun 29 '18

Brb checking out vue