<?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 Brandon Lyons on Medium]]></title>
        <description><![CDATA[Stories by Brandon Lyons on Medium]]></description>
        <link>https://medium.com/@brandonl.4231?source=rss-35eef5c8e7bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tAChCAuIePslyK9z.</url>
            <title>Stories by Brandon Lyons on Medium</title>
            <link>https://medium.com/@brandonl.4231?source=rss-35eef5c8e7bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:02:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brandonl.4231/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[Deep Dive Into The New Vue Devtools v5.0]]></title>
            <link>https://medium.com/@brandonl.4231/new-features-in-vue-devtools-v5-0-and-why-they-are-useful-3ce732fdc7a0?source=rss-35eef5c8e7bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ce732fdc7a0</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Brandon Lyons]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 01:59:48 GMT</pubDate>
            <atom:updated>2018-10-25T16:15:57.247Z</atom:updated>
            <content:encoded><![CDATA[<p>Earlier this month the Vue devtools version 5.0 beta was released, bringing amazing new features to the already debugging powerful tool. Some of the new features include performance profiling, route tracking, live editing the Vuex store, and a new settings panel. These new components have been anticipated for a while, and after getting a chance to use them for a couple weeks I wanted to share what I found to be the most helpful. Lets go through some of the new features that were added, and look at what new insights they add into the debugging process.</p><h3>Routing</h3><p>The Routing tab is brand new to the devtools suite. There are two different views here, “History” and “Routes”, that are able to be swapped by clicking on the “Routing” tab heading. Both of these give helpful information, if you are utilizing vue-router in your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ecQHJ-kCMcx_pXaFvTKtZQ.png" /></figure><p>The history view has two panels. The left-hand panel shows a history of the routes that have been traveled to. Clicking one of these history entries will show the details of that route change in the panel to the right. These details show which route the user navigated from and to, as well as any accompanying route parameters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*if3VlW_cdhVfT32qvSX26Q.png" /></figure><p>The routing view also has two panels, with the left-hand panel showing a map of all routes in the application. Clicking one of these routes will show the details for it in the right-hand panel. The details here are slightly different than the previous view, and instead will show the path, any children (nested) routes, and any route parameters.</p><h3>Vuex</h3><p>The Vuex tab is not new, but it DOES have an amazing new feature; you can now update application state right from the devtools!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*62_zLgovOrZJVQ7cU93_Mg.png" /></figure><p>This feature has been long awaited. The process for changing state was much more tedious before this update. You either had to replay the right mutations to get the state how you wanted it, or you had to manually update the default values in the Vuex module file. Now you can simply click on any state value and update or delete right from there. Additionally, you can even add new properties on existing objects!</p><figure><a href="https://blog.usejournal.com/meet-journal-d222fce8db1d"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMBwoU5bWkso8M2A1ocS9Q.png" /></a></figure><h3>Performance</h3><p>Like the routing tab, the performance tab is also a new addition. This tab is composed of two sections, “Frames per second” and “Component Render”.</p><p>The first tab, “Frames per Second” shows a live feed chart with the current fps of your application. This can be used to find certain actions or components that slow the application down.</p><p>In the picture below, you can see that the first red dip in the graph has the icons “M”, “E”, and “R” on top of it. The “M” means a mutation happened here, the “E” means an event was fired, and the “R” indicates that a route change happened. We can expect the fps of an application to dip momentarily on route changes, but if this was an unexpected dip, this would be a good indicator of which components to investigate for performance issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K24JNAacBqjXhOWPVo59Fw.png" /><figcaption>The “Frames per second” section of the Performance tab helps hone in on the cause of slowdowns</figcaption></figure><p>This second picture, of the “Component Render” tab, shows detailed time-to-run statistics for a components lifecycle methods. The left pane shows the total render time of the component, while the right pane provides a breakdown by lifecycle method. Any extremely slow components would stand out in this left tab, which again provides a good starting point for investigating performance issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wq6QjPI69Q5gvRY4A-JdNg.png" /><figcaption>The Component Render tab shows timing statistics for component lifecycle methods</figcaption></figure><h3>Settings</h3><p>Last but not least, there is a new settings menu available! Currently, this menu includes the following options:</p><ul><li>Change the display density to a more compact layout</li><li>Normalize component names (my-component would turn into MyComponent)</li><li>Update the theme — Toggles the new dark theme option on or off</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JICKD08XwYm-SBaZY_n3Kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNVLOLr24M-k8IB4BIThIQ.png" /><figcaption>New devtools settings tab, now with theme support!</figcaption></figure><h3>Conclusion</h3><p>Once again, the Vue core team and its community have gone above and beyond with providing an amazing developer tooling experience. The Vue devtools have always been an integral part of the developer experience, and this update was a huge push in the right direction. This release of devtools, combined with the recent release of the vue-cli GUI, provide an amazing development experience from creation to finish.</p><figure><a href="https://blog.usejournal.com/meet-journal-d222fce8db1d"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2IVAl0TbsfES9cFGYr40g.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ce732fdc7a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Increased the Security of My Netlify Hosted Website With This One Small Trick!]]></title>
            <link>https://medium.com/@brandonl.4231/how-i-increased-the-security-of-my-netlify-hosted-website-with-this-one-small-trick-731f4c56efd7?source=rss-35eef5c8e7bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/731f4c56efd7</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[tips]]></category>
            <dc:creator><![CDATA[Brandon Lyons]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 02:24:43 GMT</pubDate>
            <atom:updated>2018-08-03T06:24:20.674Z</atom:updated>
            <content:encoded><![CDATA[<p>How I Increased the Security of My Netlify Hosted Website With This One Small Trick! Hackers HATE It!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k7BZvJnhE3aXfrYbtjZ63w.png" /><figcaption>The title is okay because its ironic and self aware, like Deadpool</figcaption></figure><p>Security is kind of a big deal. Being instantly accessible from the internet is a double-edged sword, and Web applications are some of the most vulnerable programs because of this.</p><p>Sidebar: I have a tendency of instantly purchasing domain names when I think of a project after a late night, which is ultimately how this story comes about.</p><p>During a recent burst of motivation, I decided to create a small website with the goal of helping people get registered to vote (https://registertovote.how). I quickly wrote a prototype layout and basic functionality, but I needed a host and did not want to go through the work of setting up a DigitalOcean server (my usual hosting goto). So I turned to Netlify, my new fave for hosting anything frontend.</p><p>Everything went great! I setup my custom domains from Google Domains to point to Netlify’s DNS, added the github repo for my project to setup auto deployment, and we were off to the races! But wait, what is this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VEUZivEYNlaSg_ZyFTxTaw.png" /><figcaption>The orange and red coloring make this page look very scary</figcaption></figure><p>I got a “D” rating for security?! Wow, way to take me back to my college days, <a href="https://securityheaders.com/">https://securityheaders.com</a>. Lets fix this, shall we?</p><p>First, lets dive into what exactly security headers are. OWASP defines them as:</p><blockquote>“ The OWASP Secure Headers Project describes HTTP response headers that your application can use to increase the security of your application. Once set, these HTTP response headers can restrict modern browsers from running into easily preventable vulnerabilities. The OWASP Secure Headers Project intends to raise awareness and use of these headers.”</blockquote><p>Awesome, so these are simple HTTP response headers that we can set which will increase our website’s security. That same <a href="https://securityheaders/">https://securityheaders</a>.com site that fired a jab at my ego also provides some recommended default values for a few of these common headers. Use these recommended values (they are usually the most secure) unless you have a specific use case preventing you from doing so. Those recommended defaults are as follows:</p><pre>X-Frame-Options: DENY<br>X-XSS-Protection: 1; mode=block<br>Referrer-Policy: no-referrer<br>X-Content-Type-Options: nosniff</pre><p>So now we have some secure, sane default values for the headers, but how do we deploy them to Netlify? After a bit of searching I found out that Netlify allows you to add security headers by adding a _headers file to the root of your website’s deployed folder. If you are using a static site, this file should go right next to your index.html file. If you are using a framework like Vue.js, the file should go in the /public folder.</p><p>Paste the following code into the _headers file:</p><pre>/*<br> X-Frame-Options: DENY<br> X-XSS-Protection: 1; mode=block<br> Referrer-Policy: no-referrer<br> X-Content-Type-Options: nosniff</pre><p>The /* at the top tells Netlify to apply these headers to all possible pages/routes of your site. If you need different pages to have different security headers, you can define multiple paths in the file. You can find more information on Netlify’s headers page <a href="https://www.netlify.com/docs/headers-and-basic-auth/#custom-headers">here</a>.</p><p><strong>Note: </strong>If for any reason you cannot place a _headers file in your root web directory, you can instead create a netlify.toml file in the root of your github repository. The contents of that file will need to be slightly different than above:</p><pre>[[headers]]<br>  for = &quot;/*&quot;<br>  [headers.values]<br>    X-Frame-Options = &quot;DENY&quot;<br>    X-XSS-Protection = &quot;1; mode=block&quot;<br>    Referrer-Policy = &quot;no-referrer&quot;<br>    X-Content-Type-Options = &quot;nosniff&quot;</pre><p>Now that we have the headers in place, lets go test our sites security again!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gk6D40deKyzBnBKFAuAbhw.png" /><figcaption>The green coloring makes the page much less threatening</figcaption></figure><p>Woot! An “A”, Now that’s more like it!</p><p>I hope you enjoyed this article, don’t forget to like, comment, and subscribe! I mean upvote. Wait, that’s the wrong one too. Clap! Yes, please clap if you enjoyed this article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=731f4c56efd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting To Know the New Vue-cli 3 User Interface]]></title>
            <link>https://medium.com/@brandonl.4231/getting-to-know-the-new-vue-cli-3-user-interface-a173b00128bd?source=rss-35eef5c8e7bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/a173b00128bd</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Brandon Lyons]]></dc:creator>
            <pubDate>Sat, 02 Jun 2018 01:28:37 GMT</pubDate>
            <atom:updated>2019-01-28T21:08:15.911Z</atom:updated>
            <content:encoded><![CDATA[<p>This article will assume the reader is already familiar with what the Vue.js framework and the Vue command line tools (vue-cli) are. The official docs for these topics are (<a href="https://vuejs.org/v2/guide/">https://vuejs.org/v2/guide/</a>) and (<a href="https://github.com/vuejs/vue-cli">https://github.com/vuejs/vue-cli</a>).</p><p>Yesterday (at the time of writing), the amazing Vue-core team released version beta-15 of the official Vue command line tools. One feature in particular stands out among the usual bug fixes and performance improvements, the new web based user interface for the Vue command line interface. This awesome tool allows Vue developers to graphically create a new Vue project, live monitor app performance, add plugins to an existing project, and more. This is a pretty big deal, as getting familiar with this tool can make spinning up and maintaining any type of Vue.js application a breeze. Lets dive into some of the features head on. The full change-log for this release can be found on the <a href="https://github.com/vuejs/vue-cli/blob/dev/CHANGELOG.md">vue-cli github</a>.</p><h3>New Project Creation</h3><p>Lets go through the steps of creating a new vue project from scratch.</p><ol><li>Open a new terminal/command prompt window.</li><li>Install and/or update the vue-cli tools to beta-15 with npm i -g @vue/cli</li><li>Once updated, run vue ui. You should see a message that the gui is starting with an address like http://localhost:8000. If a browser window does not automatically open then you can manually navigate to this address.</li><li>A new browser window should open that looks like the following:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uFBZjuP5PQCMZm0z2R1e0Q.png" /><figcaption>Vue ui project manager</figcaption></figure><p>5. Navigate to a folder you want to make the project in and click the green “Create a new project here” button to start the process.</p><p>6. Select the manual preset, which will then take you to the features page where you can individually include features such as Typescript support, Routing, Testing support, CSS pre-processors, and Vuex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffVCIGKijOB6e8R9IwGpQw.png" /><figcaption>Application features</figcaption></figure><p>7. Finally select any configuration options, then start the install by clicking “create project”. You should start seeing the vue cli commands happening now in the terminal you launched vue ui from.</p><p>8. Once complete, you now have a shiny new Vue.js project with just the features you want!</p><h4>Now lets look into how we can use this new ui to run our build tasks, show application metrics, and add in plugins after project creation.</h4><h3>Project Plugins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qz-8abwYyY4uJpWp_57_mg.png" /><figcaption>Many teams already have vue cli 3 plugins ready to go</figcaption></figure><p>The first section, project plugins, allows you to inject major features into your app after it has already been created. There are hundreds of public plugins available for many popular tools and frameworks. Want to add GraphQL to your app without dealing with excessive configuration? Install the Apollo plugin to get the boilerplate setup for you.</p><p>This plugin architecture has been in the cli since the v3 alpha, but the new ui makes finding and installing these plugins so painless. Spinning up a new empty project just to try out some fancy new tools or frameworks would usually take quite a bit of time figuring out how to fit all of the tools together, and this just eliminates a lot of those pain points.</p><h3>Project Configuration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YRE9rKYtYmWIbsnA67iH5w.png" /></figure><p>Anyone who has had to manually fiddle with multiple config files for tools like webpack, gulp, eslint, babel, or typescript will love the new project configuration ui. This section provides a clean interface to allow you to tweak linter/transpiler config without deep diving into the nested JSON objects of the configuration files.</p><h3>Project Tasks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RABqDB3jCagWQBVjY8h68A.png" /></figure><p>I may have been saving the best for last, as this is my favorite part of the ui. The project tasks section allows you to run your npm scripts from the gui, while providing you with detailed statistics about your application. The data provided makes it easy to see how your application would load on various connection speeds/devices, and allows developers to quickly spot which dependencies may be resource hogs.</p><p>Most functions also have options to customize functionality further, for example the gear icon next to “Start/Stop task” for vue-cli-service serve will bring up options allowing you to change NODE_ENV from dev to prod, specify if assets should be served over https, and allow the localhost url/port to be set manually.</p><h3>Conclusion</h3><p>The Vue team has provided us with a truly amazing tool and I highly recommend all Vue developers to play around with this on their side projects or personal endeavors. Since the vue-cli v3 is still in beta there may still be some buggy experiences, so it might not be safe to use this in production applications yet. I did run into one issue while exploring this but it was not ui related, it was an npm issue I was able to resolve with a configuration change.</p><p>All in all this new vue-cli user interface brings a beautiful, modern interface for some of the more mundane tasks web developers have to handle.</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2IVAl0TbsfES9cFGYr40g.png" /></a></figure><p>📝 Read this story later in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_read_later_text">Journal</a>.</p><p>🗞 Wake up every Sunday morning to the week’s most noteworthy Tech stories, opinions, and news waiting in your inbox: <a href="https://usejournal.com/newsletter/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_text">Get the noteworthy newsletter &gt;</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a173b00128bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>