<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dobromir Hristov on Medium]]></title>
        <description><![CDATA[Stories by Dobromir Hristov on Medium]]></description>
        <link>https://medium.com/@dobromir_hristov?source=rss-89ba4c120f34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vTPhziXh21T61Ydc1NOERw.png</url>
            <title>Stories by Dobromir Hristov on Medium</title>
            <link>https://medium.com/@dobromir_hristov?source=rss-89ba4c120f34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:57:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dobromir_hristov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reacting to Promises from event listeners in Vue.js]]></title>
            <link>https://medium.com/@dobromir_hristov/reacting-to-promises-from-event-listeners-in-vue-js-8959b6d03f52?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/8959b6d03f52</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[promises]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 08:51:45 GMT</pubDate>
            <atom:updated>2019-02-07T08:56:16.370Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building a button component, that changes automatically on Promise resolution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAH3EXXvPnHCO9i7ZdAwzg.jpeg" /></figure><p>Users should know the outcome of an action they performed. A common UX pattern is buttons with loading, success and error states.</p><p>Changing those states on each action, be it easy with Vue, can be tedious, with allot of repeating code. You have to assign classes, change button text, revert the state and so on.</p><p>In this post I will show you how to leverage Promises and event handlers, to automatically change a button’s state. For styling I am using Bulma, but you can easily fit this to work with your custom styles.</p><p>This post was inspired from a <a href="https://github.com/vuejs/vue/issues/7628">recent fix</a> in the release of Vue 2.6.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fp5nm9v60zj%3Fview%3Dpreview&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fp5nm9v60zj%3Fview%3Dpreview&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fp5nm9v60zj%2Fscreenshot.png&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc9ef904d203cc95dcf218652c5a40b7/href">https://medium.com/media/fc9ef904d203cc95dcf218652c5a40b7/href</a></iframe><p>Usage of the component is straight forward</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/03304c45910ecde46d17010f47c14005/href">https://medium.com/media/03304c45910ecde46d17010f47c14005/href</a></iframe><p>TLDR: Click handlers that return a promise, will be assigned using $listeners property and resolved inside the button component, changing its state based on the promise resolution. Button exposes slots for further customisation of states.</p><h4>Important points</h4><ol><li>Click handlers must return a promise in order for the button to react on it.</li><li>Button calls the click handler from an internal method.</li><li>Outer components must not know how the button handles promise states.</li><li>Button should allow for customisation of each state</li></ol><p>With those points laid out, lets build the button.</p><h4>Returning the promise</h4><p>First things first, returning the promise. Its a good practice to always return promises from functions, that way you can await them, if called from another function.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4e867bc0458c4439f7f40864c479b1b/href">https://medium.com/media/f4e867bc0458c4439f7f40864c479b1b/href</a></iframe><p>The above code is self explanatory, on each call of the onClick method, the promise from the async request is returned. If you want to catch potential errors and act accordingly, for the button to work, you need to re-throw the error again. Forgetting to do so will cause the button to show a successful state. This is not connected to building the button it self, rather how one could use it.</p><p>Using <strong>async/await</strong> syntax means you don’t need to return a promise, it will await accordingly. This can be seen in the asyncAction method.</p><h4>Calling the handler from the button</h4><p>To listen for clicks on the component, a normal click event handler is added to the button. The more complex part is passing all event listeners to the button, while overriding the click listener.</p><p>To do this, we use the handy $listeners property on the instance. It gives us reference to all the event listeners bound to the component, in an easy to use object syntax. <a href="https://vuejs.org/v2/api/#vm-listeners">Link to docs</a></p><pre>&lt;button <em>v-on</em>=&quot;listeners&quot; ...</pre><p>From the script above, we see that we use v-on to bind listeners, which is a computed property that passes all the parent event bindings, by spreading the object into a new one, overriding the click handler with a custom handleClick method on the component.</p><pre>computed: {<br>  listeners() {<br>    <em>return</em> {<br>      ...this<em>.</em>$listeners,<br>      click: this<em>.</em>handleClick<br>    }<br>  }<br>}</pre><p>This way we can not only handle clicks, but also hover and other events. Those however, will not track promise resolution, as I think its not a common use case to do so.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/62d6aaf07cef0dba0169a9f7de3a8c96/href">https://medium.com/media/62d6aaf07cef0dba0169a9f7de3a8c96/href</a></iframe><h4>Handling the state</h4><p>The handleClick method is an async function, that warps everything in a try/catch block, setting an internal isLoading property and invoking the passed click event handler via await this.$listeners.click() . We are essentially accessing the click property from the $listeners object, which is the click handler passed from the parent. Remember that we are not passing it directly, as we overrode it inside the listeners computed property.</p><blockquote>Making the method async is a handy, as that allows to <strong>await</strong> the click handler, even if it does not return a promise. To learn more about async/await check <a href="https://javascript.info/async-await">this article</a>.</blockquote><p>After the promise is resolved, we call a small helper method called resetDelayed which sets a property called isSuccess to true, reverting it back to false after X amount of time. This way we can return the button it its initial state while giving the user enough time to notice the change. In the catch block, we use the same method to set the hasError property.</p><p>In the finally block we just set the isLoading to false, indicating the end of the loading state.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d596a8df1795101f9c3583fd740b59fb/href">https://medium.com/media/d596a8df1795101f9c3583fd740b59fb/href</a></iframe><p>The resetDelayed method sets a timeout of 2s, via the time prop, after which it returns the passed property to false. One thing to mind here, is that it checks if a loading prop is passed to the component via:</p><p>this.$options.propsData.hasOwnProperty(&#39;loading&#39;)</p><p>That allows for manual override of the loading state on the button from the parent component. In such case, we probably don’t care how the promise resolves, so we skip setting isLoading or hasError entirely</p><h4>Customising the button states and behavior</h4><p>To provide some customisation, we can use slots to give the user a way to pass custom icons or text for each of the possible states. We also provide the loading prop to set the loading state manually if needed. We can even override the amount of time the button stays in success of failure state via the time prop.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d598020f56aebc2a41cc69541f2a690e/href">https://medium.com/media/d598020f56aebc2a41cc69541f2a690e/href</a></iframe><p>The computedClasses is a computed property, applying styling classes based on the current state the button is in. The loadingState is just a helper computed property, returning the the loading prop if passed, otherwise returns the internal isLoading property.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8959b6d03f52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Къде да намерим отговори на своите Vue.js въпроси]]></title>
            <link>https://medium.com/@dobromir_hristov/vuejs-ecosystem-how-to-learn-more-234888db1b8f?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/234888db1b8f</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuebulgaria]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Mon, 10 Dec 2018 12:16:42 GMT</pubDate>
            <atom:updated>2018-12-10T13:24:25.565Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PsjA573JwYntJX-6uP06Ww.jpeg" /></figure><p>В този пост ще Ви споделя няколко ресурса, които използвам за да бъда в крак с развитието на Vue екосистемата и намирам отговор на въпроси свързани с разработката на приложения. Чрез тях, ще намерите отговори на много въпроси, ще научите нови неща, дори имате възможността да се запознаете с някои от хората, които разработват Vue ежедневно.</p><h4>Къде да намеря отговори на своите въпроси?</h4><p>Всеки програмист знае, че първото място, в което трябва да потърси е Google. Там ще намерите най-често резултати от StackOverflow, които не винаги са удовлетворителни.</p><h4>Vue Docs</h4><p><a href="https://vuejs.org/v2/guide/">Introduction - Vue.js</a></p><p>Официалната Vue документация е считана за една от най-добрите в света. Търсачката е наистина много добра и търси както в API-то, така и в Guides секцията.</p><p>Силно препоръчвам да потърсите първо в нея, преди да започнете да задавате въпроси към долупосочените места. Възможно е отговора, който търсите вече да е там.</p><h4>Vue Forum</h4><p><a href="http://forum.vuejs.org/">Vue Forum</a></p><p>За щастие, Vue има форум, в който можете да намерите отговор на по-голяма част от основните въпроси, свързани с разработката на Vue.js приложения. Форумът е сравнително активен и повечето теми имат развит отговор и решение. Това трябва да е първото място, на което да зададете въпрос, ако не намирате отговор никъде другаде.</p><h4>Vue Land — Official Vue Chat</h4><p><a href="https://vue-land.js.org/">Vue Land</a></p><p>Vue Land е официалният Vue Chat с повече от 2000 постоянно активни потребителя. Той има богат набор от тематични канали, в които хората споделят своят опит, задават въпроси и споделят мнение. Провеждат се Live Q&amp;A сесии с core Vue devs, където всеки може да зададе въпрос към тях. Модераторите постоянно поддържат нивото на спам до минимум.</p><p>#need-help секцията е доста активна, потребители и модератори постоянно си помагат един на друг по различни development въпроси. Отбийте се през #vue-testing секцията, може да се засечем :)</p><h4>Twitter</h4><p><a href="https://twitter.com/VueJSBulgaria">VueJS Bulgaria (@VueJSBulgaria) | Twitter</a></p><p>Twitter не е просто поредната социална мрежа. Това е първото място, където програмисти от цял свят споделят своите постижения, споделят проблеми, публикуват новини за пакети, анкети, обновления, статии и още много други. Отвореният модел на платформата позволява всеки да последва всеки, а краткият формат на Twitter съобщенията водят до малки и структурирани постове.</p><p>Последвайте VueBulgaria в Twitter за повече информация свързана с предстоящи Vue събития в България, интересни публикации и други.</p><p>Ето и списък с популярни хора във Vue екосистемата, който ще Ви даде добър старт в социалната мрежа.</p><p><a href="https://medium.com/hypefactors/list-of-influential-twitter-profiles-in-the-vue-js-community-state-of-2018-cca15ec1144a">List of influential Twitter profiles in the Vue.js community — state of 2018</a></p><h4>Vue Github Issues</h4><p><a href="https://github.com/vuejs/vue/issues">vuejs/vue</a></p><p>Vue Github или по-точно неговата Issues секция е пълна с по-задълбочени въпроси, когато форумът просто не е бил достатъчен или някой е попаднал на кофти проблем. Силно препоръчвам да потърсите добре за вече зададен подобен въпрос, преди да пишете нов. Въпроси без примерен линк за пресъздаване на проблема и подробно описание просто се затварят. Използвайте github като последен ресурс за помощ.</p><h4>Тематични</h4><p>Ако използвате frameworks като <a href="https://vuetifyjs.com/en/">Vuetify</a>, <a href="https://quasar-framework.org/">Quasar</a>, <a href="https://nuxtjs.org/">Nuxt </a>или др, потърсете техните форум или Discord Chat. Повечето имат собствени, където човек може да зададе по-задълбочени въпроси свързани с дадения framework.</p><h4>Обучителни ресурси</h4><p>Ако се чудите, кой Vue курс да започнете, може да разгледате линка отдолу. В него съм описал едни от най-известните курсове и личното ми мнение за тях, като ресурси, от които лично съм се учил.</p><p><a href="https://medium.com/hypefactors/a-brief-review-of-vue-learning-resources-state-of-2018-9f9ea0a08a89">A brief review of Vue learning resources — State of 2018</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=234888db1b8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hooks are coming to steal your Mixins]]></title>
            <link>https://medium.com/hypefactors/hooks-are-coming-to-steal-your-mixins-667bed17e916?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/667bed17e916</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[hooks]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Wed, 31 Oct 2018 15:59:08 GMT</pubDate>
            <atom:updated>2018-10-31T15:59:08.813Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4anlUVZgDCn92KmTt9k0AA.jpeg" /><figcaption>Pumpkin carved with Love for Vue by me :)</figcaption></figure><p>Happy Halloween Vuempires and Zombiettes!!!</p><p>Hooks are the cats pajamas right now in the React world. Everyone and their grandma is hooking up! Yes, this will be one of those posts, full of puns. Sorry not sorry</p><h3>So what are Hooks actually?</h3><p>They are a pretty nifty way of extracting away state logic from components, using a sort of shared functions. Think of it as external state services that can be plugged in and composed into components.</p><p>But that doesn’t really explain allot now does it. What best than the source of the whole thing — React Conf 2018</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fdpw9EHDh2bM%3Fstart%3D410%26feature%3Doembed%26start%3D410&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ddpw9EHDh2bM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fdpw9EHDh2bM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/54ab6341f16e9a3c22cf67f83fd02d99/href">https://medium.com/media/54ab6341f16e9a3c22cf67f83fd02d99/href</a></iframe><blockquote>I would advise you watch the whole thing, doesn’t matter that its React specific, the concept is the same.</blockquote><p>Another good read is from the React Docs — <a href="https://reactjs.org/docs/hooks-intro.html">https://reactjs.org/docs/hooks-intro.html</a> Just skip to the good parts, no need to read their Classes problems.</p><p>Now, where does Vue plug into this thing? Here is what Evan has to say about it, in a nutshell:</p><h3>Evan You on Twitter</h3><p>As a composition mechanism, hooks is objectively better than mixins, HOCs and render props. I think we will try to find a way to allow Vue users leverage its power in a way that complements Vue&#39;s idiomatic API.</p><p>Caught your attention? Does this mean Mixins are going away? Nah, don&#39;t think so. The Vue community has been quite disturbed by this thought, and been spamming all over, so I don&#39;t think the Vue team will do that.</p><p>Rather think of it as a cool extra feature. Like how the React folks have done it, optional. And it didn’t take long to get a Proof of Concept going on.</p><p><a href="https://github.com/yyx990803/vue-hooks">yyx990803/vue-hooks</a></p><p>This is an example implementation by Evan You — Vue creator, that shows it’s quite possible to use the Hooks concept it the Vue ecosystem. As a POC its not production ready at all, so please do not start implementing it like the React folks. Everyone is rewriting their plugins now… can’t blame em, those classes some times were pretty… eh. Anyway…</p><p>Vue has Mixins, and they do an awesome job for the majority of cases. They are easy to read, can be mixed into a component and boom, you are sharing logic. However they come just short when it comes to more advanced use cases, like name collisions or composing Functional Components that have their own state.</p><p>You can use Hooks to extract in-component state management logic and reuse that logic by composing it back into multiple other components.</p><h4>Example counter component Evan did, but with extracted internals.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fm5pvjp3zpx&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fm5pvjp3zpx&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fm5pvjp3zpx%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/28d977917bb8f376551563a4208989a1/href">https://medium.com/media/28d977917bb8f376551563a4208989a1/href</a></iframe><h4>Example using a functional component as just a plain template</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fx2o0wl884&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fx2o0wl884&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fx2o0wl884%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/7790253c3e10912ae800d7a24dc1415f/href">https://medium.com/media/7790253c3e10912ae800d7a24dc1415f/href</a></iframe><p>Here is a short post that got featured in the Vue Newsletter this week, explaining it a bit further.</p><p><a href="https://medium.com/@shuvohabib/vue-js-hooks-and-react-js-hooks-at-a-glance-fe5623e9ac52">Vue JS hooks and React JS Hooks at a glance</a></p><p>For more info you could checkout the whole Twitter thread that Evan started and many people came with pretty good arguments:</p><p><a href="https://twitter.com/youyuxi/status/1056670607121760257">https://twitter.com/youyuxi/status/1056670607121760257</a></p><p>You can also take a look at Scoth.io’s take on the React side of things— <a href="https://scotch.io/tutorials/getting-started-with-react-hooks">https://scotch.io/tutorials/getting-started-with-react-hooks</a></p><p>This Facebook thread is also hot right now on the topic</p><p><a href="https://www.facebook.com/groups/vuejsdevelopers/permalink/549590575452963/">Anthony Gore</a></p><p>I my self am still figuring out how I could mix hooks into my daily workflow. Stay tuned for more updates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=667bed17e916" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypefactors/hooks-are-coming-to-steal-your-mixins-667bed17e916">Hooks are coming to steal your Mixins</a> was originally published in <a href="https://medium.com/hypefactors">Hypefactors</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[List of influential Twitter profiles in the Vue.js community — state of 2018]]></title>
            <link>https://medium.com/hypefactors/list-of-influential-twitter-profiles-in-the-vue-js-community-state-of-2018-cca15ec1144a?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/cca15ec1144a</guid>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[influencers]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Tue, 25 Sep 2018 15:12:56 GMT</pubDate>
            <atom:updated>2019-02-13T18:29:39.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElZRfVOxRSdETK9Hs-sKPw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/O6TOOAtv13A?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Victor Benard</a> on <a href="https://unsplash.com/search/photos/swallow-bird-animal?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The Vue.js ecosystem is rapidly expanding. With its growth in popularity, the amount of library authors and contributors increases every day. But how does one actually manage to stay on top of the wave all the time? How do other people always know about that new plugin, or that new library that you never heard of?</p><p>In this article I will share with you a long list of outstanding people, both for Vue and JavaScript in general, which you should follow on Twitter. As strange as it may sound to some of you, Twitter is, for me, the number one place to catch the latest news in the tech world.</p><blockquote>For a curated list of Vue learning resources, please take a look at my previous article - <a href="https://medium.com/hypefactors/a-brief-review-of-vue-learning-resources-state-of-2018-9f9ea0a08a89">A brief review of Vue learning resources — State of 2018</a></blockquote><h4>TLDR:</h4><p>If you are too lazy to read the whole article, you can check the list of people on twitter below:</p><p><a href="https://twitter.com/d_m_hristov/lists/influential-vue-people">@d_m_hristov/Influential Vue people on Twitter</a></p><h4>Newsletters:</h4><p>There are so many good tech newsletters out there, that I am probably not aware of, so I will try to cover mostly what is directly related to Vue.</p><p><a href="https://news.vuejs.org/">Official Vue.js News</a></p><p>The Official Vue.js News. Produced by<a href="https://twitter.com/DamianDulisz"> <strong>@DamianDulisz</strong></a><strong> </strong>,<a href="https://twitter.com/venticco"> <strong>@ventic</strong></a><a href="https://twitter.com/greggpollack"><strong>co</strong> <strong>@greggpollack</strong></a> and<a href="https://twitter.com/AdamJahr"> <strong>@AdamJahr</strong></a>. They do weekly newsletters, covering the latest stories from Vue conferences, tutorials, plugins, hot tweets and more. The guys at <a href="https://twitter.com/VueMastery"><strong>VueMastery </strong></a>— Gregg and Adam are also doing an audio podcast of each issue of the newsletter.</p><p><a href="https://vuejsfeed.com/">Vue.js Feed</a></p><p>Vuejsfeed is curated by<a href="https://twitter.com/kostaskafcas"> <strong>@kostaskafcas</strong></a> co-author of Majesty of Vue. He also showcases tutorials, tweets, awesome new plugins and more.</p><p><a href="https://vuejsdevelopers.com/">Vue.js Developers</a></p><p>Vuejsdevelopers, maintained by <a href="http://twitter.com/anthonygore"><strong>@anthonygore</strong></a>, has the benefit of having its own blog. This means that you will receive new tutorials from the blog first if you are subscribed to the newsletter.</p><h4>Twitter Profiles:</h4><p>Below is a list of popular Vue.js contributors, core team members and developers, passionate about Vue in general. Keep in mind I have left out some core devs or contributors just because they are not active in social media.</p><ul><li><a href="https://medium.com/u/4f198f5f1f12">Evan You</a>— <a href="https://twitter.com/youyuxi"><strong>@youyuxi</strong></a><strong> </strong>— Creator<a href="https://twitter.com/vuejs"> @<strong>vuejs</strong></a></li><li><a href="https://medium.com/u/9bafe4e8ffdd">Guillaume CHAU</a> — <a href="https://twitter.com/Akryum"><strong>@Akryum</strong></a> — <a href="https://twitter.com/vuejs">@<strong>vuejs</strong></a> Core Team, works on VueCLI, Devtools and VueApollo</li><li><a href="https://medium.com/u/c2509fce86ff">Sarah Drasner</a> — <a href="https://twitter.com/sarah_edo"><strong>@sarah_edo</strong></a> — Sr. Developer <a href="https://twitter.com/Microsoft">@<strong>Microsoft</strong></a>.|<a href="https://twitter.com/vuejs"> @<strong>vuejs</strong></a> Core Team</li><li><a href="https://medium.com/u/1a6318bb9a19">Jen Looper</a><strong> — </strong><a href="https://twitter.com/jenlooper"><strong>@jenlooper</strong></a> — <a href="https://twitter.com/VueVixens">@<strong>VueVixens</strong></a> founder. <a href="https://twitter.com/ProgressSW"><strong>@ProgressSW</strong></a></li><li>Thorsten Lünborg — <a href="https://twitter.com/Linus_Borg"><strong>@Linus_Borg</strong></a> — Vue.js core team member</li><li><a href="https://medium.com/u/866bc83ce0b3">Damian Dulisz</a> — <a href="https://twitter.com/DamianDulisz"><strong>@DamianDulisz</strong></a> —<a href="https://twitter.com/vuejs"> @<strong>vuejs</strong></a> Core Team |<a href="https://twitter.com/vueconf"> @<strong>vueconf</strong></a> organizer | <a href="https://twitter.com/greggpollack">Curator of</a><a href="https://t.co/EpucZ6n72O"> http://news.vuejs.org</a></li><li><a href="https://medium.com/u/ddf9968e902c">Gregg Pollack</a> — <a href="https://twitter.com/greggpollack"><strong>@greggpollack</strong> </a>— <a href="https://twitter.com/VueMastery">@<strong>VueMastery</strong></a> | Co-host official Vue News Podcast (<a href="https://t.co/EpucZ6n72O">http://news.vuejs.org</a>)</li><li><a href="https://medium.com/u/b95265420612">Adam Jahr</a> — <a href="https://twitter.com/AdamJahr"><strong>@AdamJahr</strong></a><strong> — </strong><a href="https://twitter.com/VueMastery">@<strong>VueMastery</strong></a> | Co-host official Vue News Podcast (<a href="https://t.co/EpucZ6n72O">http://news.vuejs.org</a>)</li><li><a href="https://medium.com/u/498f8fe0ad12">Chris Fritz</a> —<strong> </strong><a href="https://twitter.com/chrisvfritz"><strong>@chrisvfritz</strong></a> — Consultant | <a href="https://twitter.com/vuejs">@<strong>vuejs</strong></a> core team member | Vue docs curator</li><li><a href="https://medium.com/u/fce17dffad0e">Eduardo San Martin Morote</a> —<strong> </strong><a href="https://twitter.com/posva"><strong>@posva</strong> </a>— <a href="https://twitter.com/vuejs">@<strong>vuejs</strong></a> core team member | Organizer of<a href="https://twitter.com/vuejsparis"> @<strong>vuejsparis</strong></a></li><li>Blake Newman — <a href="https://twitter.com/blakenewman"><strong>@blakenewman</strong></a> — <a href="https://twitter.com/vuejs">@<strong>vuejs</strong></a> core team | Organizer of<a href="https://twitter.com/vue_london"> @<strong>vue_london</strong></a> conference!</li><li><a href="https://medium.com/u/15ad6870b9ad">Sebastien Chopin</a> — <a href="http://twitter.com/Atinux"><strong>@Atinux</strong> </a>— Author of<a href="https://twitter.com/nuxt_js"> <strong>@nuxt_js</strong></a></li><li>Alexander Chopin — <a href="https://twitter.com/_achopin"><strong>@_achopin</strong></a> — Author of<a href="https://twitter.com/nuxt_js"> <strong>@nuxt_js</strong></a></li><li><a href="https://medium.com/u/82ac64561d1">Alex Jover Morales</a> — <a href="https://twitter.com/alexjoverm"><strong>@alexjoverm</strong></a> — <a href="https://twitter.com/vuejs">@<strong>vuejs</strong></a> core team partner. Instructor<a href="https://twitter.com/eggheadio"> <strong>@eggheadio</strong></a> and<a href="https://twitter.com/alligatorio"> <strong>@alligatorio</strong></a></li><li><a href="https://medium.com/u/29f499dc71d6">Alex Kyriakidis</a> — <a href="http://twitter.com/hootlex"><strong>@hootlex</strong></a><strong> —</strong><a href="https://twitter.com/vuejs"> @<strong>vuejs</strong></a> Core Team | Teacher at<a href="https://twitter.com/VueSchool_io"> @<strong>VueSchool_io</strong></a> | Author of<a href="https://twitter.com/tmvuejs"> @<strong>tmvuejs</strong></a></li><li><a href="https://medium.com/u/bdecd935ca2">Michał Sajnóg</a> — <a href="http://twitter.com/michalsnik"><strong>@michalsnik</strong></a> — Tech Lead Developer<a href="https://twitter.com/netguru"> @<strong>netguru</strong></a> |<a href="https://twitter.com/vuejs"> @<strong>vuejs</strong></a> Core Team member</li><li>Rahul Kadyan — <a href="https://twitter.com/znck0"><strong>@znck0</strong></a> — Core Team Member<a href="https://twitter.com/vuejs"> <strong>@vuejs</strong></a>. Organiser<a href="https://twitter.com/VueBLR"> <strong>@VueBLR</strong></a>.</li><li>Pine Wu<strong> — </strong><a href="https://twitter.com/octref"><strong>@octref</strong></a> — VSCode Vetur plugin author</li><li>Egoist — <a href="https://twitter.com/_egoistlily"><strong>@_egoistlily</strong></a> — Vue core team — major open source contributor</li><li><a href="https://medium.com/u/cfd681ad8836">Edd Yerburgh</a> — <a href="http://twitter.com/EddYerburgh"><strong>@EddYerburgh</strong></a> ‏ —author vue-test-utils | <a href="https://www.manning.com/books/testing-vuejs-applications">Testing Vuejs Applications</a></li><li><a href="https://medium.com/u/e397693fb21a">Roman Kuba</a> ‏- <a href="https://twitter.com/Codebryo">@<strong>Codebryo</strong></a> — <a href="http://codeship.com/">codeship.com</a></li><li><a href="https://medium.com/u/1821180d5748">Victoria Ninni Bergquist</a> —<a href="https://twitter.com/vicbergquist"> <strong>@vicbergquist</strong> </a>— Organiser of <a href="https://twitter.com/CSSFrankfurt"><strong>@CSSFrankfurt</strong></a> &amp; <a href="https://twitter.com/vuejsfrankfurt"><strong>@vuejsfrankfurt</strong></a></li><li>Natalia Tepluhina — <a href="https://twitter.com/N_Tepluhina"><strong>@N_Tepluhina</strong></a> — <a href="https://twitter.com/VueVixens">@<strong>VueVixens</strong></a></li><li>Krzysztof Jung — <a href="https://twitter.com/venticco"><strong>@venticco</strong></a> — Senior FE developer <a href="https://twitter.com/monterail">@<strong>monterail</strong></a> | Curator of<a href="http://news.vuejs.org/"> http://news.vuejs.org</a></li><li><a href="https://medium.com/u/cddb89520009">Krutie Patel</a> <strong>— </strong><a href="https://twitter.com/KrutiePatel"><strong>@KrutiePatel</strong></a> — <a href="https://twitter.com/nuxt_js"><strong>@nuxt_js</strong></a><a href="https://twitter.com/vuejs"> <strong>@vuejs</strong></a> enthusiast</li><li>Kostas Maniatis — <a href="https://twitter.com/kostaskafcas"><strong>@kostaskafcas</strong></a> — Curator of<a href="https://twitter.com/vuejsfeed"> <strong>@vuejsfeed</strong></a> | author of<a href="https://twitter.com/tmvuejs"> @<strong>tmvuejs</strong></a></li><li>Igor Randjelovic — <a href="https://twitter.com/igor_randj"><strong>@igor_randj </strong></a>— NativeScript-Vue author</li><li><a href="https://medium.com/u/7728756e245a">Tiago Alves</a> — <a href="http://twitter.com/tiagoreisalves"><strong>@tiagoreisalves</strong> ‏ ‏ </a>— NativeScript-Vue</li><li><a href="https://medium.com/u/803b03599f6">Ben Hong</a> — <a href="http://twitter.com/bencodezen"><strong>@bencodezen</strong></a> — <a href="https://twitter.com/vuedc">@<strong>vuedc</strong></a> &amp;<a href="https://twitter.com/vuemeetups"> @<strong>vuemeetups</strong></a> co-founder</li><li><a href="https://medium.com/u/eb09c1f97a07">Jilson Thomas</a> — <a href="http://twitter.com/jilsonthomas"><strong>@jilsonthomas</strong></a> — Co-Founder of<a href="https://t.co/B2EweScwxi"> http://VueJobs.com </a>| Organiser of<a href="https://twitter.com/VueToronto"> @<strong>VueToronto</strong></a></li><li>John Leider — <a href="https://twitter.com/zeroskillz">@<strong>zeroskillz</strong></a>— Creator of Vuetify</li><li>Phan An —<a href="https://twitter.com/notphanan"> @<strong>notphanan</strong></a><strong> — </strong><a href="https://twitter.com/vuejs">@<strong>vuejs</strong></a> core team member</li><li>Israel Ortuño — <a href="https://twitter.com/IsraelOrtuno">@<strong>IsraelOrtuno</strong></a></li><li>James McGlasson —<strong> </strong><a href="https://twitter.com/jamesvuejs"><strong>@jamesvuejs</strong></a><strong> — </strong>Organiser/Head of Marketing and Enterprise at <a href="https://twitter.com/frontend_love">@<strong>frontend_love,</strong></a><strong> </strong><a href="https://twitter.com/vuejsamsterdam">@<strong>vuejsamsterdam</strong></a> <a href="https://twitter.com/angularnl">@<strong>angularnl,</strong></a><strong> </strong><a href="https://twitter.com/vuejsroadtrip">@<strong>vuejsroadtrip</strong></a></li></ul><h4>Profiles of Vue related websites, blogs, learning material</h4><ul><li><a href="https://twitter.com/VueLandDiscord"><strong>@VueLandDiscord</strong></a> — Official VueJS Discord chat server</li><li><a href="https://twitter.com/VueNewsletter">@<strong>VueNewsletter</strong></a> ‏ — Official Vue newsletter page</li><li><a href="https://twitter.com/MadeWithVueJS">@<strong>MadeWithVueJS</strong></a> — General Vue.js news</li><li><a href="https://twitter.com/VueSchool_io">@<strong>VueSchool_io</strong></a> ‏ — Official page of <a href="http://vueschool.io/">Vueschool.io</a></li><li><a href="https://twitter.com/VueMastery">@<strong>VueMastery</strong></a><strong> —</strong> Official <a href="http://vuemastery.com/">VueMastery </a>page.</li><li><a href="https://twitter.com/VuejsJob">@<strong>VuejsJob</strong></a> ‏ ‏ —Official<a href="http://vuejobs.com/"> VuejsJobs </a>page</li><li><a href="https://twitter.com/VueComponents">@<strong>VueComponents</strong></a> ‏ — Tweets about new released components and plugins</li><li><a href="https://twitter.com/vuejsdevelopers">@<strong>vuejsdevelopers</strong></a> — Official <a href="http://vuejsdevelopers.com/">Vuejsdevelopers</a> page‏</li><li><a href="https://twitter.com/vuejsradar">@<strong>vuejsradar</strong></a> ‏ —Official <a href="https://t.co/MWWKKRfDTL">vuejsradar.com</a> page.</li><li><a href="https://twitter.com/alligatorio">@<strong>alligatorio</strong></a> — Official <a href="http://xn--lligator-06g.io/">Alligator.io</a> page.</li><li><a href="https://twitter.com/nuxt_js">@<strong>nuxt_js</strong></a> ‏ — Official <a href="https://nuxtjs.org/">Nuxt.js</a> page</li><li><a href="https://twitter.com/vuejsamsterdam">@<strong>vuejsamsterdam</strong></a> — Official <a href="https://www.vuejs.amsterdam/">VuejsAmsterdam</a> page</li><li><a href="https://twitter.com/quasarframework">@<strong>quasarframework</strong></a> — Official QuasarFramework page</li></ul><h4>People you should definitely follow that are not strictly Vue related</h4><p>Its not all Vue though. General optimisation tips, best practices, common patterns and more are required to build a good app. Here is a list of exceptional people, who have a thing or two to teach you about JavaScript.</p><ul><li><a href="https://medium.com/u/2508e4c7a8ec">Addy Osmani</a><strong> —</strong><a href="https://twitter.com/addyosmani"><strong> @addyosman</strong></a><strong>i — </strong><a href="https://twitter.com/GoogleChrome">@GoogleChrome</a> — Author of <a href="https://addyosmani.com/resources/essentialjsdesignpatterns/book/">Learning JavaScript Design Patterns</a></li><li><a href="https://medium.com/u/393110b0b9e4">Sean T. Larkin</a> — <a href="https://twitter.com/TheLarkInn"><strong>@TheLarkIn</strong></a><strong>n — </strong>Speaker, engineer,<a href="https://twitter.com/webpack"> @<strong>webpack</strong></a> + Lerna Core Team, TPM<a href="https://twitter.com/Microsoft"> @<strong>Microsoft</strong></a><a href="https://twitter.com/EdgeDevTools"> @<strong>EdgeDevTools</strong></a>.</li><li><a href="https://medium.com/u/a11f7c00cbbe">Rich Harris</a> — <a href="https://twitter.com/Rich_Harris"><strong>@Rich_Harris</strong></a>— <a href="https://twitter.com/sveltejs">@<strong>sveltejs</strong></a> + <a href="https://twitter.com/RollupJS">@<strong>RollupJS</strong></a></li><li><a href="https://medium.com/u/db72389e89d8">Kent C. Dodds</a> — <a href="https://twitter.com/kentcdodds">@<strong>kentcdodds</strong></a> ‏ — Engineer at paypal</li><li><a href="https://medium.com/u/2bdb4734b294">Adam Wathan</a> — <a href="https://twitter.com/adamwathan">@<strong>adamwathan</strong></a>— <a href="https://twitter.com/tailwindcss">@<strong>tailwindcss</strong></a>, Advanced Vuejs Component Design course.</li><li><a href="https://medium.com/u/f11db20f3d2f">John Papa</a> — <a href="https://twitter.com/John_Papa"><strong>@John_Papa</strong></a> — Developer <a href="https://twitter.com/Microsoft">@<strong>Microsoft</strong></a></li><li><a href="https://medium.com/u/6d5456230083">Paul Irish</a> — <a href="https://twitter.com/paul_irish"><strong>@paul_irish</strong></a> — <a href="https://twitter.com/____lighthouse">@<strong>____lighthouse</strong></a> &amp;<a href="https://twitter.com/ChromeDevTools"> @<strong>ChromeDevTools</strong></a> developer</li><li><a href="https://medium.com/u/5b25bc58c2e">Mattias Petter Johansson</a> — <strong>@mpjme</strong> — <a href="https://youtube.com/funfunfunction">FunFunFunction </a>youtube channel</li><li><a href="https://medium.com/u/a789923b5cad">Chris Coyier</a> — <a href="https://twitter.com/chriscoyier"><strong>@chriscoyier</strong></a>— Co-founder<a href="https://twitter.com/CodePen"> @CodePen</a>.</li><li><a href="https://medium.com/u/7fab51e62203">Axel Rauschmayer</a>a — <a href="https://twitter.com/rauschma"><strong>@rauschma</strong></a> — Author of blog<a href="https://twitter.com/2ality"> @2ality</a>, book<a href="https://twitter.com/ExploringJS"> @ExploringJS</a></li><li><a href="https://medium.com/u/9ea60eb6fc7c">Christoph Nakazawa</a> — <a href="https://twitter.com/cpojer"><strong>@cpojer</strong></a> — Dev at Facebook, Jest, Yarn</li><li><a href="https://medium.com/u/f87cd234b9d9">Jake Archibald</a> — <a href="https://twitter.com/jaffathecake"><strong>@jaffathecake</strong></a> — Developer advocate for Google Chrome.</li><li><a href="https://medium.com/u/b384aa92a080">Sara Vieira</a> — <a href="https://twitter.com/NikkitaFTW">@<strong>NikkitaFTW</strong></a>— developer at <a href="https://twitter.com/YLDio">@<strong>YLDio</strong></a></li><li><a href="https://twitter.com/filrakowski">Filip Rakowski — @<strong>filrakowski</strong></a> — Co-founder<a href="https://twitter.com/VueStorefront"> @<strong>VueStorefront</strong></a></li><li><a href="https://medium.com/u/ee6691f0bd65">Ives van Hoorne</a> — <a href="https://twitter.com/CompuIves">@<strong>CompuIves</strong></a> — Creator of<a href="https://t.co/o00zRCZSGx"> </a><a href="https://codesandbox.io/">https://codesandbox.io</a></li><li><a href="https://medium.com/u/6c00c4569299">Chris DeMars</a> — <a href="https://twitter.com/saltnburnem">@<strong>saltnburnem</strong></a> — a11y expert</li><li>Kitze — <a href="http://twitter.com/thekitze">@<strong>thekitze</strong></a> — Founder of<a href="https://reactacademy.io/"> https://reactacademy.io</a> |<a href="http://twitter.com/sizzyapp">@<strong>sizzyapp</strong></a> |<a href="https://twitter.com/jsui_app"> @<strong>jsui_app</strong></a></li></ul><p>Waw that was a long list. Most of these people are actively posting, sharing ideas and discussing hot, trendy topics. Pick the ones you think suit your interests best and follow in their footsteps.</p><p>If you think I left out someone who should really be in the list, leave a comment bellow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cca15ec1144a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypefactors/list-of-influential-twitter-profiles-in-the-vue-js-community-state-of-2018-cca15ec1144a">List of influential Twitter profiles in the Vue.js community — state of 2018</a> was originally published in <a href="https://medium.com/hypefactors">Hypefactors</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A brief review of Vue learning resources — State of 2018]]></title>
            <link>https://medium.com/hypefactors/a-brief-review-of-vue-learning-resources-state-of-2018-9f9ea0a08a89?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f9ea0a08a89</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Sun, 09 Sep 2018 06:08:45 GMT</pubDate>
            <atom:updated>2018-09-10T21:41:13.147Z</atom:updated>
            <content:encoded><![CDATA[<h3>A brief review of Vue learning resources — State of 2018</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eP1aHgzlOWgmASjO_nLpfw.png" /></figure><blockquote>When it comes to mastering any skill, you’re not going to learn everything you need to know from one book. This is why blossoming frameworks like Vue.js need a lot of educational producers. It’s good for everyone, and everyone will need lots of educational resources on their way to mastery. <strong><em><br></em>Gregg Pollack</strong></blockquote><p>This quote has so much truth in it. No matter how many books I read, podcasts I listen to or videos I watch, there is always something new to pick up.</p><p>In this post, we will go through both premium and free learning resources, so there will be something for everyone. Some of these may be a bit steep for someone just starting out, but split with a friend, ask your boss to pay for it, look out for sales, in the end it will surely pay off.</p><p>The times when the Vue docs were the only learning resource are long gone. There is so much quality material out there that you cannot read it all.</p><p>I will go through the ones that helped me become a full-time Vue developer and a lead developer at <a href="https://hypefactors.com/">Hypefactors</a>.</p><h3>Premium material</h3><h4>Vue JS 2 — The Complete Guide (incl. Vue Router &amp; Vuex)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*XWtU9iQtJMn6CV9BOQ6Gyg.jpeg" /></figure><p><strong>Author</strong>: <a href="https://twitter.com/maxedapps">Maximilian Schwarzmüller</a></p><p><strong>Link</strong>: <a href="https://www.udemy.com/vuejs-2-the-complete-guide/">https://www.udemy.com/vuejs-2-the-complete-guide/</a></p><p>This is probably the cheapest course you can buy. Udemy make sales all the time, so for around 10 bucks, you can grab the whole course. It was the first video course I bought, specially for Vue.</p><p>Maximilian does a great job at explaining things and he also has follow up videos on YouTube that are worth checking out. Plus he covers other topics as well.</p><p>The course covers all the important topics, from the Vue basics, props, form handling, Vuex, Vue Router and others. He is also updating the course, from what I saw, he has added Vue CLI 3 in there.</p><h4>Majesty of Vue 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*qyJtkCA9Yuyqm0t9BdpTRQ.jpeg" /></figure><p><strong>Authors:</strong> <a href="https://twitter.com/hootlex">Alex Kyriakidis </a>, <a href="https://twitter.com/kostaskafcas">Kostas Maniatis</a></p><p><strong>Link: </strong><a href="https://leanpub.com/vuejs2">https://leanpub.com/vuejs2</a></p><p>The first edition was probably the first book ever released about Vue development in general. The second edition did not disappoint as well. It covers, again, all the important topics a novice Vue developer should read on: props, events, two way binding, component communication and much more. Each section is packed with lots of examples and tips.</p><p>The first part of the book does not use the CLI, ES6 or anything like that, so novice devs can get straight into development in the browser. At a later point it continues with Webpack, SFC’s, what transpilation is and so on. There is no Vuex or Vue Router material, from what I remember, it’s more dedicated to Vue it self.</p><h4>Laracasts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ITuPxmB_amys8TlXIDJvBw.png" /></figure><p><strong>Author</strong>: <a href="https://twitter.com/jeffrey_way">Jeffrey Way</a></p><p><strong>Link</strong>: <a href="http://laracasts.com/">http://laracasts.com/</a></p><p>Now I know, this is not a Vue specific resource, its Laravel oriented… but hear me out. Jeffrey Way was one of the first people who started pushing video content about Vue, back when it was v0.12!!! His efforts along with Taylor’s affinity for Vue pushed it to be the de facto front-end framework for Laravel. And Laravel is currently dominating the PHP realm.</p><p>Now don’t get me wrong, Jeffrey is no Vue guru, he does however do a magnificent job at showing a variety of different use cases, like reusing components, charts, mixins, object oriented form handling and many more. I am talking about actual components and patterns, things you can actually use, not the lame todo app we have all done a million times already.</p><p>A subscription will get you access to allot of Laravel related tutorials as well! Laravel is a perfect framework for building API’s for Vue, I should know, I’ve used it many times and our <a href="https://hypefactors.com/">Hypefactors</a> API is written on Laravel 5.6 at the time of writing. This makes Laracasts an even more appetizing bite because you will learn how to build your API as well as your App.</p><p>Not only that, but Jeffrey is such a good teacher, that I bet once you go through a few videos, you will want more. The “<em>jump into the dom</em>” and “<em>lets cache this</em>” phrases keep ringing in the back of my head, some of you know what I mean.</p><h4>Vue Mastery</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TAgWwNK-0EKw5pxBwEs2hA.png" /></figure><p><strong>Authors: </strong><a href="https://twitter.com/greggpollack">Gregg Pollack</a> , <a href="https://twitter.com/AdamJahr">Adam Jahr</a></p><p><strong>Link</strong>: <a href="https://www.vuemastery.com/">https://www.vuemastery.com/</a></p><p>This is the most recent one I’ve gone through and to be honest I was mostly focused at the Advanced Components series and I have to say, I liked them. Listening about Vue’s reactivity, proxies, Virtual DOM and how it works was actually really interesting to me, plus having Evan there to explain things made it even cooler. What better than the man himself, right?</p><p>Both Gregg and Adam are veterans in video tutorials and do an amazing job at visually explaining things with code, animations, icons, arrows and so on.</p><p>They do have introduction videos, which are free, ranging from Vue basics like events, prop binding, communication, forms to real world examples, like Single File components, Vue Router, Axios, with Vuex just around the corner.</p><p>Keep in mind they are constantly pushing new content so new material is probably available by the time you are reading this.</p><p>Not to mention they host the official Vue Newsletter podcast and share screen recordings of the Vue Conf US. More on that bellow.</p><p>Alright, so we dipped our toes into more advanced stuff, so let’s continue in the same manner.</p><h4>Advanced Vue Component Design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8FD_hMuXivXbVbq_czWzcw.png" /></figure><p><strong>Author</strong>: <a href="https://twitter.com/adamwathan">Adam Wathan</a></p><p><strong>Link</strong>: <a href="https://adamwathan.me/advanced-vue-component-design/">https://adamwathan.me/advanced-vue-component-design/</a></p><p>Adam Wathan is a popular figure in the Laravel community. He has an exceptional book about testing Laravel and his recent project <a href="https://tailwindcss.com/">Tailwind CSS</a> spread like wildfire, it’s pretty rad, go try it out.</p><p>The course is a tad bit on the pricey side, but it goes on sale from time to time. If you are serious about using Vue for big apps its a no brainer.</p><p>He covers so many of the pain points we all have had when using Vue in the real world. Ranging from implementing external libraries, modals, slots, scoped slots, render functions and many many more.</p><p>This is not a course for new developers. It uses ES6+ features, SFC, slots and all the good stuff.</p><p>I personally had a blast going through it, even though I have been a Vue dev for a long time, I picked up a few useful techniques.</p><h4>Testing Vue Applications</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/399/1*iB7P8RJHtDrWzVnoA8UCFw.jpeg" /></figure><p><strong>Author: </strong><a href="https://twitter.com/EddYerburgh">Edd Yerburgh</a></p><p><strong>Link: </strong><a href="https://www.manning.com/books/testing-vuejs-applications">https://www.manning.com/books/testing-vuejs-applications</a></p><p>You do test your apps, right? Right? Hehe :)</p><p>Any serious developer knows they should unit and e2e test their code. The author Edd Yerburgh is the guy behind <a href="https://vue-test-utils.vuejs.org/">@vue/test-utils</a>, a utility library for testing Vue applications and he wrote this book about testing Vue apps. The book recently went out of MEAP and is an exceptional learning resource.</p><p>He covers all the necessary topics for testing Vue apps — testing components, mixins, Vuex, Vue Router, mocking dependencies, mocking the store, it’s all there. On top of that there is a plethora of examples in the Hackernoon clone he made on GitHub. The book does make the assumption the reader is a novice Vue developer so spends a good part of each section explaining what will be done and how. I found that a bit boring, so I just skipped to the meat of it, tests.</p><p>He uses Jest for unit tests which for me is a no brainer. Jest is awesome! Heard of snapshot testing? You will :) E2E tests are done with Nightwatch, which I personally don’t like as much as Cypress, but that’s a minor detail. You can adapt to whatever framework you like.</p><p>I bought the book when it was just released as a MEAP, and I think I have gone through it fully two times.</p><p><strong>Resources I have not had the chance to try but look pretty solid</strong></p><h4>Fullstack Vue</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*wyjeSgsNA7Qn9Usv3dT4-g.png" /></figure><p><strong>Authors: </strong><a href="https://twitter.com/djirdehh">Hassan Djirdeh</a>, <a href="https://twitter.com/eigenjoy">Nate Murray,</a> <a href="https://twitter.com/auser">Ari Lerner</a></p><p><strong>Link</strong>: <a href="https://www.fullstack.io/vue/">https://www.fullstack.io/vue/</a></p><p>Man that cover… I want to have it on my bookshelf.</p><p>This book looks like a pretty cool introduction into using Vue with a backend, though it states nowhere what backend they use. Looking at the table of contents you will learn about SFC’s, Events, Vuex, Routing, even a bit of tests in there. Price is decent and they have experience with other trendy frameworks like React, React Native and Angular.</p><h4>Vue School</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OF4Utj3k_NFNC0oLLeKwOg.png" /></figure><p><strong>Author</strong>: <a href="https://twitter.com/hootlex">Alex Kyriakidis</a></p><p><strong>Link</strong>: <a href="https://vueschool.io/">https://vueschool.io/</a></p><p>Vue School is developed by one of the core Vue developers and the co author of Majesty of Vue — Alex Kyriakidis, lessons are curated by Rolf Haug and the Vue docs man himself, Chris Fritz. The website offers free courses like integrating Vue with Firebase db and Firebase authentication, Vuex and more.</p><p>The premium course shows how to build a forum and covers a variety of topics like Plugins, Webpack configs, SEO, Linting, Form Handling, Firebase DB, authorization and much much more. What I noticed is, the course covers a wide range topics, from the general ones we’ve all seen, to real world pain points one might end up with.</p><p>Definitely worth checking out.</p><h4>Learn Advanced Vue.js Features from the ground up</h4><p><strong>Author:</strong> <a href="https://twitter.com/youyuxi">Evan You</a></p><p><strong>Link: </strong><a href="https://frontendmasters.com/courses/advanced-vue/">https://frontendmasters.com/courses/advanced-vue/</a></p><p>OK so this is not a course for everyone. This course is probably for those who are already well into Vue and really want to know how the engine works under the hood. Just looking at the topics: Reactivity, Writing Plugins, Render Functions, you know its getting real.</p><p>The course is authored by the Vue.js creator Evan You him self, if that isn&#39;t awesome, i don&#39;t know what is.</p><p>I confess I have not had the opportunity to buy and go through it, but its on the list.</p><h4>Enterprise Vue</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DxAXRptT9fc3IFvHMSGecA.png" /></figure><p><strong>Author</strong>: <a href="https://twitter.com/anthonygore">Anthony Gore</a></p><p><strong>Link</strong>: <a href="https://vuejsdevelopers.com/courses/enterprise-vue">https://vuejsdevelopers.com/courses/enterprise-vue</a></p><p>Not yet released, but by the looks of it, will be also jam packed with good stuff. The author, Anthony Gore is the man behind Vuejsdevelopers.com, one of the first blogs about Vue development. Keep an eye out for it.</p><p><strong>Free material</strong></p><h4>Vuejsdevelopers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*XRaNxZ5tDPp8fw_d_LoGgw.png" /></figure><p><strong>Authors</strong>: <a href="https://twitter.com/anthonygore">Anthony Gore</a> and contributors</p><p><strong>Link</strong>: <a href="http://vuejsdevelopers.com/">http://vuejsdevelopers.com/</a></p><p>We just mentioned Anthony’s future course, so let’s look into his blog. Vuejs Developers is a one stop shop for all things Vue. Articles are original, revolve around a variety of topics and touch new and emerging tech, plus they are curated by Anthony himself.</p><h4>Alligator.io</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*BnnPlBONR2vvtge61AOiOw.png" /></figure><p><strong>Link</strong>: <a href="https://alligator.io/vuejs/">https://alligator.io/vuejs/</a></p><p>I swear this is both the weirdest and coolest name ever. They have a lot of material in all kinds of Vue related topics, and not only. I do mean all kinds, Vuepress, TypeScript, various plugins, Vue CLI.</p><h4>Vue-enterprise-boilerplate</h4><p><strong>Author</strong>: <a href="https://twitter.com/chrisvfritz">Chris Fritz</a></p><p>The man behind the Vue docs, Chris Fritz, made this ever updating and evolving repo, jam packed with best practices for when your App gets into enterprise territory. I kid you not, I look at it every week… at least.</p><p>It has tips on using code generators for common boilerplate, Vuex module tricks, first class tests, its pure gold.</p><h4>Views on Vue</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*uiMFciiAKy5zIgWUoaB7sg.jpeg" /></figure><p><strong>Author</strong>: <a href="https://twitter.com/chrisvfritz">Chris Fritz</a> and guests</p><p><strong>Link</strong>: <a href="https://devchat.tv/views-on-vue/">https://devchat.tv/views-on-vue/</a></p><p>Speaking about Chris, he co-hosts this awesome Vue podcast. Cool guests, good vibe, dev jokes everywhere, good stuff. I listen to it when driving, alone, away from interruption. You can find also other cool podcasts on devchat, related to not only Vue.</p><h4>Official Vue Newsletter</h4><p>Authors: <a href="https://twitter.com/damiandulisz">Damian Dulisz,</a> <a href="https://twitter.com/venticco">Krzysztof Jung,</a> <a href="https://twitter.com/greggpollack">Gregg Pollack,</a> <a href="https://twitter.com/AdamJahr">Adam Jahr</a></p><p>Link: <a href="https://news.vuejs.org/">https://news.vuejs.org/</a></p><p>One of the best ways to learn about the new things in the Vue.js world is by subscribing to the weekly Vue newsletter. Every week the authors go through the most important news, new released tutorials, hot tweets, plugins and more, serving it all in a curated, easy to glance through manner.</p><p>Did I mention they also have an audio podcast of each issue? How cool is that! Want to hear your name get mentioned there? Go, contribute to the Vue ecosystem, write a plugin, make a guide, I know I loved it.</p><h4>Official Vue Docs</h4><p>Link: <a href="https://vuejs.org/v2/guide/">https://vuejs.org/v2/guide/</a></p><p>Vue is well known for having one of the best docs out there, and you better believe it. Allot of examples, good separation of functionality, easy introduction for novices.</p><p>The docs are constantly being improved and worked upon so give them a check from time to time. New gems appear all the time.</p><p>There is also the <a href="https://vuejs.org/v2/cookbook/">Official Vue Cookbook</a>. It is a superb collection of tips and tricks from various contributors, revised and curated by <a href="https://twitter.com/sarah_edo">Sarah Drasner</a>.</p><p>The <a href="https://vuejs.org/v2/style-guide/">Official Style Guide</a> is also a good resource on how to structure your components.</p><h4>Conference workshops</h4><p>Did you know that Vue experts and core team members from around the world do workshops at conferences? No? Well now you do.</p><p>You can buy a ticket to a Vue conference + a whole day at one of those workshops and be thought by the leading people in the Vue branch. Dont miss out on the opportunity to ask those people questions, live and in person. You get the added bonus of hanging out at the after party with some of the coolest devs on earth.</p><h4>In conclusion</h4><p>I shared a lot of resources, most of which I personally have gone through and can vouch for.</p><p>Premium courses of course handle more detailed and advanced topics, in a more linear and curated manner, whereas blogs typically share a variety of topics by many authors.</p><p>Which one to pick? What do you prefer? Video or books? What is your budget? Go through their table of contents and decide.</p><p>There is no better one, you cannot read one book and say I know it. You have to go through a handful of videos and articles, then apply what you’ve learned in the real world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f9ea0a08a89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypefactors/a-brief-review-of-vue-learning-resources-state-of-2018-9f9ea0a08a89">A brief review of Vue learning resources — State of 2018</a> was originally published in <a href="https://medium.com/hypefactors">Hypefactors</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Vue.js Form Validation with Vuelidate]]></title>
            <link>https://medium.com/js-dojo/simple-vue-js-form-validation-with-vuelidate-722331e5ab0d?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/722331e5ab0d</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 00:00:00 GMT</pubDate>
            <atom:updated>2020-05-07T03:06:07.179Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVjduU244kDytiGwuoFrmg.png" /></figure><p>Thanks to Vue’s reactivity model, it’s really easy to roll your own form validations. This can be done with a simple method call on the form submit, or a computed property evaluating input data on each change.</p><p>Using your form validation can quickly become cumbersome and annoying, however, especially when the number of inputs in the form increase, or the form structure gets more complicated e.g. multi-step forms.</p><p>Thankfully, there are great validation plugins for Vue like <a href="https://github.com/monterail/vuelidate">Vuelidate</a>. In this article, we’ll be looking at how Vuelidate can be used to simplify:</p><ul><li>Validation</li><li>Multi-step form validation</li><li>Child component validation</li><li>Error messages</li></ul><p>We’ll also see how the <a href="https://github.com/dobromir-hristov/vuelidate-error-extractor">Vuelidate-error-extractor</a> plugin can be used to simplify error message display per input, or as an error summary above or below the form.</p><blockquote>Note: this article was originally posted <a href="https://vuejsdevelopers.com/2018/08/27/vue-js-form-handling-vuelidate/?utm_source=medium-vjd&amp;utm_medium=article&amp;utm_campaign=fhv">here on the Vue.js Developers blog</a> on 2018/08/27</blockquote><h3>Basic validation with Vuelidate</h3><p><strong>Vuelidate</strong> is data-model oriented, meaning validation rules are added to a validations object in the component definition, rather than being added directly to input elements in the DOM.</p><p>The structure must resemble that of the form object, but the number of validation rules can be dynamic and change depending on which fields need validation.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4993f4d0b558f6dc8a1cd104997904e1/href">https://medium.com/media/4993f4d0b558f6dc8a1cd104997904e1/href</a></iframe><p>Here’s a live example:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2F6y93q20wyr&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2F6y93q20wyr&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2F6y93q20wyr%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f6b31d9050b39ddd490876fb64516e1/href">https://medium.com/media/8f6b31d9050b39ddd490876fb64516e1/href</a></iframe><h3>Defining custom validators</h3><p>Out of the box validation rules in Vuetify will work for most cases, but every so often you’ll need a custom validator.</p><p>With <strong>Vuelidate</strong>, each validation rule is a function that returns a Boolean or Promise resolving to a Boolean. This means you can predefine your own validators in a validators.js file and just import each validator when needed.</p><p>Custom validators receive the currently validated data as a first param, and the whole data context as a second. For example, if you have a form data object and you are validating the email property, the first param will be the email itself and the second will be the whole data object.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8312b4fba51c4b60683534175e785ad/href">https://medium.com/media/b8312b4fba51c4b60683534175e785ad/href</a></iframe><p>You can also create custom validators with the help of a few special helpers that come packed with <strong>Vuelidate</strong>. Check out the <a href="https://monterail.github.io/vuelidate/#custom-validators">Custom Validators</a> section in the Vuelidate docs for examples.</p><h3>Dynamically changing rules</h3><p>Being able to change the validation rules on the fly can be a godsend with multi-step forms. Each step has its own rules that validate certain parts of the form data.</p><p><strong>Vuelidate</strong> can use computed properties as validation rules. That means that you can return different rules for each step of a multi-step form.</p><p>In the example below, validations is now a function returning an object, rather just an object. This means it will be called after the component is initialized and computed properties are run.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb1cd73def94aedb6a11e9a95888b3b6/href">https://medium.com/media/eb1cd73def94aedb6a11e9a95888b3b6/href</a></iframe><h3>Breaking down large forms into child components</h3><p>Once a form gets bigger, you might want split up your form into several smaller components to avoid having a mega component handling all the form validation.</p><p>However, storing form data in separate components rather than in a single place makes collecting the data harder. You could loop each child component via a ref binding and get the data, either implementing a data fetcher method or naming the form data in a specific way.</p><p>Another way is to store form data in Vuex, where you define all the rules on the parent and create a computed property referencing the store’s form state. Pass down the validator to each component if needed.</p><blockquote><em>Tip: if using Vuex for form data, try the </em><a href="https://github.com/maoberlehner/vuex-map-fields"><em>vuex-map-fields</em></a><em> plugin to reduce boilerplate by setting each field as a computed property.</em></blockquote><p>For most cases, I keep all the data and validation rules on a parent wrapping component that passes down the relevant validator to each child as a prop and handles sending the data to the server.</p><p>Each smaller component then uses the $touch() method on its validator prop to note that data is being changed and emits changed data via $emit(&#39;input&#39;, value) for easy v-model binding.</p><p>To make the validator available to all children, you have a few options:</p><ul><li>Pass it down as a prop to each component</li><li>Use the <a href="https://medium.com/@znck/provide-inject-in-vue-2-2-b6473a7f7816">Provide/Inject API</a></li><li>Create a new Vue instance in the store itself. Check <a href="https://gist.github.com/autumnwoodberry/d56d4f28d987b846c5216b2142586f7c">this gist</a> on how that might work</li></ul><p>Here’s a live example of the first method i.e. passing the down as a prop to each component. This is the simplest to comprehend and in most situations will be the one you will want to use.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fnnxy0wjpwm&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fnnxy0wjpwm&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fnnxy0wjpwm%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2db60aae5cea3b565f9c0912f229e7d/href">https://medium.com/media/c2db60aae5cea3b565f9c0912f229e7d/href</a></iframe><p>Once we’ve covered error message display, I’ll show you an example using the Provide/Inject API.</p><h3>Validation error display</h3><p>So the form is in place, its validated on each key press, but what about displaying error messages to the users?</p><p>We can just check each validator for errors and color our inputs, but what if we wanted to show a message? What if there is a need to display more than one error at a time? If/else checks start flying around everywhere.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a1bccf95924c438ad42b17accd9960f/href">https://medium.com/media/1a1bccf95924c438ad42b17accd9960f/href</a></iframe><p>As you can see there is a lot of repetition there, a lot of checking, you need to know what validators each field has. Adding a new rule means you have to go and edit the template too.</p><h3>Error display with Vuelidate-error-extractor</h3><p>There is a better way! <strong>Vuelidate-error-extractor</strong>, which I wrote, does the heavy lifting for you by extracting all the errors for each field, finding the appropriate error message for each rule and displaying it. It gives the user a flexible way of displaying errors with minimal boilerplate and repetitiveness.</p><p>You can use one of the built-in templates for Bootstrap and Foundation or just as easily build our own to suit your needs. All you need to do is register the plugin, define an object containing common error messages and register the template you want to use. We will refer to the single input error display as singleErrorExtractor</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fmjxzpvpw6j%3Ffrom-embed&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fmjxzpvpw6j%3Ffrom-embed&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fmjxzpvpw6j%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/317c1b314c1a069fc225e348b76a049a/href">https://medium.com/media/317c1b314c1a069fc225e348b76a049a/href</a></iframe><h3>Creating custom error display components</h3><p><strong>Vuelidate-error-extractor</strong> loops the validations for each form data and checks each rule if it’s valid or not. The invalid ones are then extracted and a validation error message is assigned to them.</p><p>The bundled singleErrorExtractorMixin provides a set of helper methods and computed properties to assist the developer with building their own input error display.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3fd27cef7861d4a0bdd3688b2a2d2b66/href">https://medium.com/media/3fd27cef7861d4a0bdd3688b2a2d2b66/href</a></iframe><p>Now just wrap your input with the new component:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4576c8333ad4876e7f3e4656300e03a8/href">https://medium.com/media/4576c8333ad4876e7f3e4656300e03a8/href</a></iframe><p>Check out <a href="https://dobromir-hristov.github.io/vuelidate-error-extractor/custom_templates.html">custom templates docs</a> for a detailed explanation on how to make your own error display.</p><p>Being so flexible means that you can adapt it to any Vue UI framework you wish. Here is a list of popular UI frameworks and examples how to implement it for each one: <a href="https://dobromir-hristov.github.io/vuelidate-error-extractor/other_frameworks.html">https://dobromir-hristov.github.io/vuelidate-error-extractor/other_frameworks.html</a></p><h3>Form error summary</h3><p>Sometimes you need to have a summary of all the errors in a form, be it on top or at the bottom.</p><p>You can use the prebuilt components for Foundation or Bootstrap, use the baseMultiErrorExtractor component or the multiErrorExtractor mixin. For 90% of use cases, the baseMultiErrorExtractor will suffice.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d403e0e1b6c1e2aab03825c2c7f24d9/href">https://medium.com/media/6d403e0e1b6c1e2aab03825c2c7f24d9/href</a></iframe><p>It will reuse the same error messages that you defined up front for the singleErrorExtractor to use. The $validator must be passed as a prop.</p><p>To be able to assign a proper field label to each error, it requires an object called attributes to be defined where the error messages were defined. This object represents a map annotating how each field should be called, i.e. { name: &quot;Name&quot;, email: &quot;Email&quot; }.</p><h3>Reducing boilerplate by injecting the validator</h3><p>Passing the validator and attribute prop to each form input and the multiErrorExtractor can get annoying quite fast, not to mention the boilerplate.</p><p>To overcome this, you can use the provided form-wrapper component to inject the validator down to all inputs.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1fa8cb4decb7819c5e371b4c1c5f311e/href">https://medium.com/media/1fa8cb4decb7819c5e371b4c1c5f311e/href</a></iframe><p>This method uses the Provide/Inject API to pass down the $validator to all the components that need it. Each form-group can then drop its validator and attribute props, to be replaced by a single name prop, annotating which field in the form it represents.</p><p>It will also try to figure out the input’s attribute property by checking the attributes object we defined earlier.</p><h3>Summary</h3><p>Handling and validating forms on the front end as you saw, can often become a pain in the bum, especially when forms become big and need to be split up.</p><p>Using <strong>Vuelidate</strong> makes the whole ordeal a lot more bearable. In tandem with <strong>Vuelidate-error-extractor</strong>, displaying error messages under each input can go from a tedious repetitive chore, to simply adding a wrapping component or two, that do it all for you.</p><h3>Code examples</h3><ul><li><a href="https://codesandbox.io/embed/6y93q20wyr">Basic validation with Vuelidate</a></li><li><a href="https://codesandbox.io/embed/wwv80myowl">Defining custom validators</a></li><li><a href="https://codesandbox.io/embed/o979o4myjq">Dynamically changing rules</a></li><li><a href="https://codesandbox.io/embed/nnxy0wjpwm">Breaking down large forms into child components</a></li><li><a href="https://codesandbox.io/embed/4w8x04l2k0">Validation error display</a></li><li><a href="https://codesandbox.io/embed/mjxzpvpw6j">Error display with Vuelidate-error-extractor</a></li><li><a href="https://codesandbox.io/embed/l240kmxwl">Creating custom error display components</a></li><li><a href="https://codesandbox.io/embed/6v1lyz831r">Form error summary</a></li><li><a href="https://codesandbox.io/embed/0p986z74p0">Reducing boilerplate by injecting the validator</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fc6nt6t%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fc6nt6t&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a118686daa9b0788782c6985cc572d3a/href">https://medium.com/media/a118686daa9b0788782c6985cc572d3a/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722331e5ab0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/js-dojo/simple-vue-js-form-validation-with-vuelidate-722331e5ab0d">Simple Vue.js Form Validation with Vuelidate</a> was originally published in <a href="https://medium.com/js-dojo">Vue.js Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Add i18n and manage translations of a Vue.js powered website]]></title>
            <link>https://medium.com/hypefactors/add-i18n-and-manage-translations-of-a-vue-js-powered-website-73b4511ca69c?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/73b4511ca69c</guid>
            <category><![CDATA[lokalise]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[translation]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 11:27:18 GMT</pubDate>
            <atom:updated>2020-03-24T12:54:18.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGXdfl8X22zBYL-PVHp7UA.jpeg" /><figcaption>Vue + Vue Router + Vue-i18n + Lokalise.co</figcaption></figure><p>Setting up a Vue.js website with internationalization (i18n) support sounds daunting at first, but it’s actually easier than one might think. For this tutorial we will be using <a href="https://kazupon.github.io/vue-i18n/">VueI18n</a>, a great package by one of the Vue core team devs.</p><h4>TLDR:</h4><p>Checkout the <a href="https://github.com/dobromir-hristov/vue-i18n-starter">vue-i18n-starter</a> repo for a simplified Vue app with i18n support.</p><h4>Initial setup</h4><p>You need to do two main steps:</p><ol><li>Instantiate the plugin by providing a default locale, a fallback and an object containing all the translation strings.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fwq2CVXbjNtTSmUOPUNJTQ.png" /><figcaption>Setup i18n</figcaption></figure><p>2. Tell our App about that instance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wl86GFuH4ga_DWEOwCl6eQ.png" /><figcaption>Pass i18n instance to Vue app</figcaption></figure><p>That’s all it takes to have the app i18n ready. Now you can just use {{ $t(‘hello’) }} inside Vue component templates and you will get Hello.</p><h4>Changing the language</h4><p>Changing the language is as simple as setting locale in the $i18n property on the Vue instance.</p><pre><em>this.$i18n.locale = &#39;fr&#39;</em></pre><p>Now it should display hello in the language you just set, in this case french.</p><p>The actual format of the locale does not matter, as it will just search for the same key in the messages object, you can have pt_BR, pt-br, pt_br etc.</p><p>If you set a language that is not loaded in the messages, it will show the fallback language’s translation. If the translation is not available in the fallback it will just return the key, in this case hello.</p><p>Keys can be deeply nested if needed, like pages.login.title .</p><p>With that said, lets create a basic language switcher, that loops our supported languages and on click, sets the selected language to $i18n.locale .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6btvP4rxXMp_QFxp1WCI0g.png" /><figcaption>Simple language switcher</figcaption></figure><h4>Setting the language as a route parameter</h4><p>Setting it up slightly depends on how you want your URLs to look like. The most popular choice is to have the language param as the first segment of the URL <a href="http://www.website.com/en.">www.website.com/en.</a></p><p>If you are not using Vue Router to route your app, you would need to figure this next step yourself, but the idea should be the same.</p><ol><li>Check if the URL contains the language parameter</li><li>Check if the language is supported by the app. If not redirect to a supported one.</li><li>Check if the language in the param is the default one. Don’t do nothing if it is.</li><li>(Optional) async load the language strings</li><li>Change the language in the App</li></ol><h4>Making it work with Vue Router</h4><p>First you need to tell the Router about the lang parameter. Define a top level route in your Vue Router routes like shown below. All pages will be children of this route.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IKAkuBlp_olmD_nsQHttLg.png" /><figcaption>Setup routes file</figcaption></figure><p>Next initialize the Vue Router with the routes defined above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_xDWetaL2iafT9d0DsaCw.png" /><figcaption>Instantiate Router</figcaption></figure><p>Finally pass the Router instance to the main Vue instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-PZ9IgjKrX4qsmbCs6pa2w.png" /><figcaption>Pass router instance to App</figcaption></figure><p>Essentially we are creating a page whose route is a dynamic property that every time we assume is the language property.</p><p>The router can’t distinguish between website.com/en and website.com/about as both would fall into the same path matcher.</p><p>As mentioned above, all pages would need to be nested inside the children key of the top level component. <strong>About Page</strong> would become website.com/en/about and it will get rendered inside the router-view of that top level page.</p><p>If you need a page to be matched without the lang in the URL, you have to define it above the lang page definition we just added.</p><p>Checking if the lang param is valid and supported by the App can be done inside the page’s beforeEnter guard. It is a function that receives 3 parameters:</p><ol><li>the route you want to go to — <strong>to</strong></li><li>the one you come from —<strong> from</strong></li><li>callback to call when you are done — <strong>next</strong></li></ol><p>Read more about it in the <a href="https://router.vuejs.org/guide/advanced/navigation-guards.html#global-guards">VueRouter Route Guards docs</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oOAbzwODVUZxPD5O5Cnew.png" /><figcaption>Initial Router guard</figcaption></figure><p>Test the app. Go to website.com and you should get redirected to website.com/en.</p><h4>Async loading translation strings</h4><blockquote>But what about more languages?</blockquote><p>Well, we could load all our language strings in the <strong>messages</strong> object at once and it would work.</p><p>But what if we support 10 languages and each of them has 500 keys? Or 10000 keys? We would be pushing unnecessary code for all our users to load upfront, which they wont probably ever need. The more time it takes for your app to load, the more users may just quit.</p><p>What we could do is only provide the English keys by default and on demand asynchronously load the rest. If you are using Webpack this is super easy to do with the <a href="https://webpack.js.org/guides/code-splitting/#dynamic-imports">dynamic import</a> function.</p><p>We will do two things.</p><ul><li>Load the translation strings on demand (async)</li><li>Feed the strings into Vue-i18n</li></ul><p>Lets add this to the beforeEnter guard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AGLlKz1x6IZfgvwM_UiJpQ.png" /><figcaption>Async load json files</figcaption></figure><p>Now we need to extract all of the translation strings into separate json files inside the lang folder. It is a top level folder. This means the English ones as well. To make our code a bit cleaner we will just import the English strings and feed them to the i18n instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tjtiBr5bJ4-t5htqFTLV7A.png" /><figcaption>Separate language files</figcaption></figure><p>We are using the path @/lang which is an alias for the top-level folder. If you are using vue-cli its already setup for you. If not, then can do ../lang/${lang}.json.</p><h4>Using vue-i18n outside Vue components</h4><p>The way we extracted i18n instance into its own i18n.js file actually gives us the opportunity to use it in many places, where the Vue instance isn’t available and we cant use this.$i18n. Such places are:</p><ul><li>Vuex store</li><li>Route guards</li><li>beforeRouteEnter Vue hooks — the Vue instance is not not ready yet, so you can’t use this there.</li></ul><h4>Cleaning it up</h4><p>It all works, but there is some repetition and the route guard is a bit nasty. If you want to change the lang param in the html tag or set the <strong>axios</strong> Accept-language header, those would need to fit into the <strong>beforeEnter</strong> guard too.</p><p>What about checking for supported languages? Those are defined in a few places. Not really DRY.</p><p>What you could do is extract all those repetitions and fit them inside a helper service file that you can then import and use. You could also extract this into Vuex actions, but because it will not be used inside Vue components that often, it doesn’t make sense. That would also make them async.</p><p>Check out the <a href="https://github.com/dobromir-hristov/vue-i18n-starter">example i18n-starter </a>repo to see how you could refactor this to a more clean approach.</p><h4>Bonus: Managing translation strings using Lokalise</h4><p>Managing translation strings is hard work. Having to sync all language strings all the time is a drag.</p><p>Fortunately there is a super cool service to the rescue —<a href="https://lokalise.com/"> Lokalise.com</a>. Its a payed service, that has a free limited plan, but for the amount of time you are saving its well worth it. The free plan has 1 user and 500 keys, which is OK to try it out, even enough for smaller projects.</p><p>You can upload the English file as the original source, assign translators, then just download everything into separate .json files when ready. It even detects if someone messed up a {placeholder} in the translations. How cool is that?</p><p>You can also use their CLI tool to make syncing up and down even easier.</p><p>Checkout npm run lokalise:down command in package.json for info on how to make the sync-down work.</p><p>That’s it!</p><p>p.s. if you thoroughly enjoy stuff like this why not check our <a href="https://thehub.dk/jobs?search=hypefactors">job openings</a> at Hypefactors?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73b4511ca69c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypefactors/add-i18n-and-manage-translations-of-a-vue-js-powered-website-73b4511ca69c">Add i18n and manage translations of a Vue.js powered website</a> was originally published in <a href="https://medium.com/hypefactors">Hypefactors</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Busting SPA Chunk Cache for Active Users After a Deploy]]></title>
            <link>https://medium.com/hypefactors/busting-spa-chunk-cache-for-active-users-after-a-deploy-a9a06242edb1?source=rss-89ba4c120f34------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9a06242edb1</guid>
            <category><![CDATA[pusher]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[netlify]]></category>
            <dc:creator><![CDATA[Dobromir Hristov]]></dc:creator>
            <pubDate>Fri, 04 May 2018 15:02:45 GMT</pubDate>
            <atom:updated>2018-05-04T15:02:45.978Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we used Pusher to reload the user’s browser without them noticing it</h4><p>It’s a common problem with single page apps (SPA): when a deployment finishes successfully after the user has loaded the app, they still use the old and cached version until they refresh the website.</p><p>This problem aggravates with async chunks. The app is split in parts and each part is only loaded on demand, like when a user navigates to a respective section. The user might be in one part of the app while a deploy process succeeds, then if they navigate to another part, the chunks they request will have been removed from the server by the build script. Problem: this causes loading errors.</p><p>We had the same issues with <a href="https://hypefactors.com/">Hypefactors</a> and <a href="https://hype.news/">Hype.News</a>. Until we devised an elegant, yet simple solution to this problem.</p><p><a href="https://pusher.com/">Pusher</a> is the main ingredient to this solution.</p><p>On a successful deployment, the CI pushes an event to notify the frontend. There we catch and queue a page refresh. When the user starts browsing the website again, the first navigation is via a page redirect. We also guard pages where a refresh might cause loosing important page state.</p><p>This approach is technology-agnostic. At Hypefactors, we use Vue, but this solutions works equally well for React or other frameworks. And for the deploy event notification any push framework can be used. We went with Pusher because its easy to use and reliable. There is a free to try, and totally worth it. For deployments we use <a href="https://netlify.com/">Netlify</a>. It’s fast, easy to use with an integrated CDN, prerendering and so on.</p><p>Enough talk, lets see how its done.</p><h3>Prerequisites</h3><p>First you need to register the needed app environments on <a href="https://dashboard.pusher.com/accounts/sign_in">Pusher</a>. We chose to use separate pusher environments for each of our staging processes as opposed to using one for all environments. Inside each environment we created a public deployments channel.</p><p>Using one Pusher environment would require constant checking to make sure you don’t start refreshing the production app.</p><h3>Setting up the Frontend</h3><p>Create a notify-deployment.js and paste the code bellow, filling in the noted places.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*FusALDdtbjjo02xW0EC6tw.png" /></figure><p>Now every time you want to notify the frontend that a deploy was successful you do node path/to/notify-deployment.js production</p><p>Create a PusherService.js file that you can import at the bootstrap of your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9O5neBSFAwElhklQl0yzoA.png" /></figure><p>The tricky part here is to find a way to pass different pusher keys depending on the current environment (dev/staging/production). We import different config files based on the currently set NODE_ENV</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*Wc8NmsFpx0pF_OhtYm04IQ.png" /><figcaption>Import the right environment variables</figcaption></figure><p>Then we pass the variables to the app via the Webpack DefinePlugin plugin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*FWBejqKv4ypZCijivVaTAA.png" /><figcaption>Pass the variables to webpack.DefinePlugin</figcaption></figure><p>Webpack will just replace process.env.YOUR_VARIABLE with the same variable inside the config folder.</p><p>You can use this method to get access to other environment specific keys, urls and others you defined via process.env.YOUR_VARIABLE</p><p>Now when your app loads, you need to subscribe to the development channel on Pusher. We use Vue so we do this in the App’s created hook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4RSoVOJMlh0r7wW0oD8Z4w.png" /></figure><p>Now this saves a FORCE_RELOAD variable into localStorage via the persist helper we have. This gives us an easy way to reload the user’s browser when they navigate around the app. We do this using Vue router’s beforeEach hook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtKqs_3nqUqKAcx5qKEfuQ.png" /></figure><p>We check whether FORCE_LOAD is saved in localStorage and whether it is true. We use our load helper for that, which defaults to false if not set.</p><p>Next we check the route. If any of the parent matched routes is blacklisted, a.k.a. protected, it should not get refreshed, as precious form data might get lost. That means it will just wait for the next navigation event.</p><p>Finally we save FORCE_RELOAD as false and we navigate to the location we wanted via a full page refresh.</p><h3>Set up the Deployment Script</h3><p>All we need to do now is, after a successful deployment, we run the node notify-deployment --development</p><p>This will send an event to the deployment channel that you want to silently reload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LH957FXhF4-RNBwJEVgXQA.png" /><figcaption>Plugging in the deployment script into Netlify</figcaption></figure><p>We have helper commands in package.json to make this easier to read and manage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sl1usgKeoMgCzAVpZhXRWQ.png" /><figcaption>Helper commands for notifications inside package.json</figcaption></figure><p>That’s all folks!</p><p>This approach of reloading is great for continuous deployment, especially when you deploy multiple times an hour.</p><p>The code and scripts have been collected in a gist for easy copy pasting. Check out <a href="https://gist.github.com/dobromir-hristov/50df8fbdf52de942ee70552646e2eeb7">https://gist.github.com/dobromir-hristov/50df8fbdf52de942ee70552646e2eeb7</a></p><p>p.s. did you know that Hypefactors is <a href="https://thehub.dk/jobs?search=hypefactors">hiring</a>?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9a06242edb1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypefactors/busting-spa-chunk-cache-for-active-users-after-a-deploy-a9a06242edb1">Busting SPA Chunk Cache for Active Users After a Deploy</a> was originally published in <a href="https://medium.com/hypefactors">Hypefactors</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>