<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Javascript on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/javascript/</link>
    <description>Recent content in Javascript on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 22:25:45 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding React Lifecycle Methods</title>
      <link>https://www.bradcypert.com/understanding-react-lifecycle-methods/</link>
      <pubDate>Wed, 05 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/understanding-react-lifecycle-methods/</guid>
      <description>&lt;p&gt;React Lifecycle Methods are one tricky piece of business, especially if you’re coming from a framework that doesn’t have their own. Thankfully, they’re fairly similar to Android’s lifecycle methods and it wasn’t long before I was able to grasp them.&lt;/p&gt;&#xA;&lt;p&gt;React has changed a lot over the past few years and it’s lifecycle methods are no exceptions. In fact, with the release of hooks, the idea of lifecycles were shaken once more!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fetching Data with React Hooks</title>
      <link>https://www.bradcypert.com/fetching-data-with-react-hooks/</link>
      <pubDate>Thu, 09 Jan 2020 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/fetching-data-with-react-hooks/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://reactjs.org/docs/hooks-intro.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;React hooks have changed the way that I (and arguably the React Community) prefer to build components&lt;/a&gt;&#xA;. I’ve been working on a GraphQL project for a while, and when we migrated to functional components and hooks, I was able to use&lt;a href=&#34;https://www.apollographql.com/docs/react/api/react-hooks/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt; Apollo’s hooks&lt;/a&gt;&#xA; for my data fetching needs. However, I find myself now working on a new project that doesn’t use GraphQL. Consequentially, I find myself wondering “How do I fetch data with React Hooks?”&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Quick Script to Update All of Your NPM Dependencies</title>
      <link>https://www.bradcypert.com/a-quick-script-to-update-all-of-your-npm-dependencies/</link>
      <pubDate>Wed, 21 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/a-quick-script-to-update-all-of-your-npm-dependencies/</guid>
      <description>&lt;p&gt;Nothing crazy here, I’ve just found myself chaining together pipes for something that I feel should ship with NPM. You can use this script to update all of your outdated dependencies to the latest. This is something you’ll want to do cautiously, definitely don’t run this and commit it without testing. However, if you have a pretty solid test suite, you can integrate something like this into your CI pipeline and fix forward should you find any issues. Anyways, without further ado, here’s the script.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A brief summary on Automated Testing</title>
      <link>https://www.bradcypert.com/a-brief-summary-on-automated-testing/</link>
      <pubDate>Sat, 20 Aug 2016 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/a-brief-summary-on-automated-testing/</guid>
      <description>&lt;p&gt;I recently read this &lt;a href=&#34;https://www.toptal.com/javascript/writing-testable-code-in-javascript&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;amazing article&lt;/a&gt;&#xA; by &lt;a href=&#34;https://twitter.com/joshmock&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Josh Mock&lt;/a&gt;&#xA; and felt the need to share it. In fact, the tools he uses in his examples – JavaScript, Mocha+Chai, and Phantom are the tools I use daily to do the same thing.&lt;/p&gt;&#xA;&lt;p&gt;I can’t stress enough how great his article is, especially if you’ve written some tests before but you’re not sure how to write a &lt;strong&gt;good&lt;/strong&gt; test. That being said, there’s a few more things I’d like to cover and add to it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>JavaScript: Generators</title>
      <link>https://www.bradcypert.com/javascript-generators/</link>
      <pubDate>Tue, 19 Jul 2016 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/javascript-generators/</guid>
      <description>&lt;p&gt;One thing I’ve learned recently from Clojure (don’t worry, this post &lt;strong&gt;is&lt;/strong&gt; about JavaScript) is that laziness is great. Lazy code is powerful code, allowing you to model things like infinite sequences or complex computations over a range of data. Without this laziness, an infinite sequence would cause a stack overflow or complex computations would bog down your performance when you may not even need to perform all those computations to begin with!&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Brief Comparison of FlowRouter and Iron:Router for Meteor.js</title>
      <link>https://www.bradcypert.com/a-brief-comparison-of-flowrouter-and-iron-router-for-meteor-js/</link>
      <pubDate>Fri, 11 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/a-brief-comparison-of-flowrouter-and-iron-router-for-meteor-js/</guid>
      <description>&lt;p&gt;Recently, I was updating an open source package that I maintain – &lt;a href=&#34;http://www.github.com/bradcypert/ignite&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;a project structure scaffolding tool&lt;/a&gt;&#xA;. While updating the template I use for my Meteor apps, I realized my tool was still catering towards Iron:Router. For those unaware, Iron:Router has a history of being &lt;strong&gt;the&lt;/strong&gt; Router for Meteor apps. When I first used it, however, it felt like it was lacking in some ways. After using it on about several Meteor apps now, I’ve adjusted my design to conform to Iron:Router and it works extremely well, but recently &lt;a href=&#34;http://www.kadira.io&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;KadiraHQ&lt;/a&gt;&#xA; created their own Router – FlowRouter – and oh, is it nice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
