<?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 Do Async on Medium]]></title>
        <description><![CDATA[Stories by Do Async on Medium]]></description>
        <link>https://medium.com/@doasync?source=rss-f88c2255dc26------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*VL6bn351mM8Axgkd_AS8dw.jpeg</url>
            <title>Stories by Do Async on Medium</title>
            <link>https://medium.com/@doasync?source=rss-f88c2255dc26------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:59:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@doasync/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[Why you need your own Starter Kit]]></title>
            <link>https://blog.devgenius.io/why-you-need-your-own-starter-kit-210fef1278b9?source=rss-f88c2255dc26------2</link>
            <guid isPermaLink="false">https://medium.com/p/210fef1278b9</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[starter-kit]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Do Async]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 11:35:58 GMT</pubDate>
            <atom:updated>2020-07-09T18:45:25.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aIqwVmhPFxsnIGtvg8_oxg.jpeg" /></figure><p>JavaScript has hugely changed in the last few years. It is not easy to accept so many changes all at once. One big shift that was happening was building. We went from a very simple thing, including our JavaScript with script tags, to having build steps that compile our language to a huge incomprehensible file. Starting from scratch really isn’t practical anymore.</p><p>The number of options that are available in the JavaScript space today is overwhelming. There are a lot of decisions that we might consider when creating a robust JavaScript development environment. Decision overload shouldn’t affect the entire team on every new project. A team should make all of these decisions just once.</p><p>Also, the tooling is one of the hardest part of JavaScript nowadays. There are so many complex dependencies that it takes a long time to set up a new app. Yes, it’s good to know how everything works, but that doesn’t mean you need to learn it all before getting started. It’s better to learn as you go. Getting off the ground quickly allows you to focus more on the code and avoid getting discouraged by difficult setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ckCN69fULWAfMwHgPylWg.png" /></figure><p>Today many teams have their own development environment. You may have heard terms like Boilerplate, Starter Kit, Skeleton App or Example Project. There are many benefits to building your own development environment. You are free to select the best and most relevant technologies for your needs. You can build it in a way that fits your team best and put only those features that you care about. This helps avoid unnecessary complexity, makes it easy to fix bugs and tweak the setup as time passes. Any existing boilerplate projects are likely to contain technologies that you don’t want or need, or it can be time-consuming and error-prone removing features or tweaking how they work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*VhB0nSWEiQiVCwKI68M7Yg@2x.png" /></figure><p>Is it worth building your own starter kit? Well first, it codifies a long list of decisions, agreed tools, best practices, and lessons learned. It also encourages consistency. It protects you from forgetting important details. It increases quality because doing the right thing becomes automatic. And finally, it avoids repeating work. You shouldn’t have to think about how to handle minification, automation, transpiling, bundling, cache-busting and more every time you start a new project. A starter kit encapsulates all these decisions for you, it’s like a living, automated, and interactive checklist. It makes sure the right things get done even when you’re in the heat of the moment. Doing the right thing becomes an easy thing, that’s a big win.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5DycIPTV6Ns4NLYmX-lMg.png" /></figure><p>There are so many steps involved in doing things right, that it’s easy to overlook a step. The list of best practices in JavaScript has become too long for most people to hold in their heads. When you find something new that everyone should start doing, you now have a place that you can codify the practice so that it happens automatically from now on. A well-structured development environment provides rapid feedback on your work, quickly reporting on any linting, testing, or compilation errors the moment that you hit save. It assures the developer doesn’t overlook important concerns or make common mistakes along the way. So, it can be a good idea to make your own starter kit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210fef1278b9" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/why-you-need-your-own-starter-kit-210fef1278b9">Why you need your own Starter Kit</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effector: powerful and fast 5kb state manager]]></title>
            <link>https://codeburst.io/effector-state-manager-6ee2e72e8e0b?source=rss-f88c2255dc26------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ee2e72e8e0b</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Do Async]]></dc:creator>
            <pubDate>Thu, 25 Apr 2019 03:00:26 GMT</pubDate>
            <atom:updated>2021-02-18T13:44:28.526Z</atom:updated>
            <cc:license>https://creativecommons.org/publicdomain/mark/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*QRAHCSt3aRwfUpx9zqsxag.png" /></figure><p>Effector is a state manager for any JavaScript app (React/Vue/Node.js). It allows you to manage data in complex applications without the risk of inflating the monolithic central store.</p><h4>Key features</h4><ul><li>multiple stores</li><li>computed values (no need for memoization)</li><li>side-effect management (async actions)</li><li>statically typed (TypeScript/Flow/Reason)</li><li>framework agnostic</li><li>less boilerplate by design</li><li>relatively small size</li><li>optimized for speed</li></ul><h4>Simple example</h4><p>Counter app using React + hooks</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/93b53624d5947009d99e6a9b59d00302/href">https://medium.com/media/93b53624d5947009d99e6a9b59d00302/href</a></iframe><p>👆 <a href="https://share.effector.dev/epAix7Ae">Try it</a></p><h4>Principles</h4><ul><li>Application stores should be as light as possible — the idea of adding a store for specific needs should not be frightening or damaging to the developer.</li><li>Application stores should be freely combined — application data can be statically distributed, showing how it will be converted in runtime.</li><li>Autonomy from controversial concepts — no decorators, no need to use classes or proxies — this is not required to control the state of the application and therefore the library uses only functions and simple JavaScript objects.</li><li>Predictability and clarity of API — a small number of basic principles are reused in different cases, reducing the user’s workload and increasing recognition. For example, if you know how .watch works for events, you already know how .watch works for stores.</li><li>The application is built from simple elements — space and way to take any required business logic out of the view, maximizing the simplicity of the components.</li></ul><p><strong>GitHub </strong>★<strong>: </strong><a href="https://github.com/zerobias/effector">https://github.com/zerobias/effector</a></p><h3>Core concepts</h3><pre>import {createEvent, createStore, createEffect} from &#39;effector&#39;</pre><h4>Event</h4><p>Event — is something that happens. Trigger it with some arguments to do some action.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/71fce149461f2e355257901b749f4419/href">https://medium.com/media/71fce149461f2e355257901b749f4419/href</a></iframe><h4>Store</h4><p>Store — an object that holds the state. There can be multiple stores.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9105b66206175070fce8a99a811e673c/href">https://medium.com/media/9105b66206175070fce8a99a811e673c/href</a></iframe><h4>Effect</h4><p>Effect is a container for an async function. It triggers its done/fail events.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/63e3688cb231dc33908c07c6f0494406/href">https://medium.com/media/63e3688cb231dc33908c07c6f0494406/href</a></iframe><h4>combine</h4><p>You can combine many stores into a single computed one.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e768ed6c16ee5c5dfa8856335b6ce10/href">https://medium.com/media/2e768ed6c16ee5c5dfa8856335b6ce10/href</a></iframe><h3>Codesandbox</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fm7k7y70l49&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fm7k7y70l49&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fm7k7y70l49%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/fbdfb470c17d7ecec7391450f22041ec/href">https://medium.com/media/fbdfb470c17d7ecec7391450f22041ec/href</a></iframe><h3>API Reference</h3><p><a href="https://effector.now.sh/docs/api/effector/effector">https://effector.now.sh/docs/api/effector/effector</a></p><p>…</p><p>Modern state management libraries solve some problems, but they have problems themselves to a greater or lesser degree, because of which the developer sometimes has to strain more than he could.</p><p>Effector is an integrated approach to solving a problem, an attempt to do everything at once. And the attempt is quite successful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ee2e72e8e0b" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/effector-state-manager-6ee2e72e8e0b">Effector: powerful and fast 5kb state manager</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redux-thunk vs. async generators]]></title>
            <link>https://codeburst.io/redux-thunk-generators-fec5337827e?source=rss-f88c2255dc26------2</link>
            <guid isPermaLink="false">https://medium.com/p/fec5337827e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Do Async]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 03:43:58 GMT</pubDate>
            <atom:updated>2017-12-18T21:47:21.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*QvMA3wuR73Bl15nef6NYOA.jpeg" /></figure><p>Yeah, you can use ES6+ generators as your action creators. You might not need <strong>redux-thunk</strong> anymore.</p><h3>Usage</h3><p>How can generators help? You can yield action objects to dispatch them! No wrapping each time with dispatch:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*_3P8KbEwQBFa_-0zjkWglQ.png" /><figcaption>Async generator as an action creator</figcaption></figure><p>When you invoke a generator, its body is not executed, but <em>iterator</em> object is returned instead. You usually wrap your action creators into a dispatch call, so <em>iterator</em> will be dispatched to the store. You’ll need some redux middleware to handle <em>iterators</em>. Here it is:</p><p><a href="https://www.npmjs.com/package/redux-iterate">redux-iterate</a></p><p>This middleware handles ‘nextable’ objects. It calls iterator’s next() method and generator function&#39;s body is executed step by step. Generator yields actions and they are dispatched to the store.</p><p>How you can get the state? yield <strong>always</strong> returns a new state. You can yield nothing (undefined), if you just want to get the current state (nothing will be dispatched):</p><pre><em>// Inside generator:</em></pre><pre>let state <strong>=</strong> <strong>yield;<br><br>or</strong></pre><pre>const params <strong>=</strong> getParamsFromState(<strong>yield</strong>); <em>// yield expression</em></pre><p>You can also return some data from generator and get it with .then:</p><pre>signIn().then(username =&gt; {<br>   console.log(username);<br>});</pre><h3>Further refactoring</h3><p>More than that, if you use this lib: <a href="https://www.npmjs.com/package/redux-action-creators"><strong>redux-action-creators</strong></a></p><p>… you can get rid of type constants and additional actions in order to define your action creator in one block of code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*reUT8V2q1qbhHWMOmff_BQ.png" /></figure><p>It kinda ‘generates’ sub-types for your action creators and is a very handy tool.</p><p>Have fun with Redux!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fec5337827e" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/redux-thunk-generators-fec5337827e">Redux-thunk vs. async generators</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Promisify objects immutably]]></title>
            <link>https://codeburst.io/do-async-js-c0bfa6ce1536?source=rss-f88c2255dc26------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0bfa6ce1536</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Do Async]]></dc:creator>
            <pubDate>Mon, 31 Jul 2017 16:12:01 GMT</pubDate>
            <atom:updated>2017-08-25T08:24:01.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*0vz0kDMg4zmki7elsRWOZw.jpeg" /><figcaption>Little cute hammer ;)</figcaption></figure><p>Hey! I’m a tiny little npm module - <strong>doasync</strong>. 50 lines of code! Don’t ignore me, I’m very helpful! With me you can call any method of your object as if it was promisified! The object will not be modified. No extra variables and objects! Cool, ha?</p><pre>doAsync(fs).readFile(&#39;package.json&#39;, &#39;utf8&#39;).then(result =&gt; {...})</pre><p>I can promisify functions as well not only objects and <strong>util.promisify</strong> guy helps me. But before we go, we must thank and give all credit to <strong>Proxy</strong> and <strong>ES6</strong> guys… <strong>WeakMap</strong> has also proved useful.</p><h3>Let’s go!</h3><p>Like one kid said, util.promisify() (which is under the hood of this module) can interact directly with the V8 API, so it doesn&#39;t create closures and will be faster than userland implementations. Here is some more examples of the usage:</p><pre>const fs <strong>=</strong> require(&#39;fs&#39;);<br>const doAsync <strong>=</strong> require(&#39;doasync&#39;);</pre><pre>doAsync(fs).readFile(&#39;package.json&#39;, &#39;utf8&#39;).then((result) =&gt; {<br>    console.dir(JSON.parse(result), {colors<strong>:</strong> true});<br>});</pre><h3>With functions</h3><p>For example with request library:</p><pre>doAsync(request)(&#39;http://www.google.com&#39;).then(({body}) =&gt; {<br>   console.log(body);<br>   <em>/* ... */<br></em>});</pre><p>You can even use native call and apply to bind some context:</p><pre>doAsync(myFunc).apply(context, params).then(result =&gt; {<strong>...</strong>});</pre><p>Isn’t it really promising?</p><p><a href="https://github.com/doasync/doasync">https://github.com/doasync/doasync</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0bfa6ce1536" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/do-async-js-c0bfa6ce1536">Promisify objects immutably</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ESLint on steroids with Airbnb + Standard JS styles]]></title>
            <link>https://codeburst.io/eslint-with-airbnb-standard-js-sublime-text-965a1db58793?source=rss-f88c2255dc26------2</link>
            <guid isPermaLink="false">https://medium.com/p/965a1db58793</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Do Async]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 19:17:05 GMT</pubDate>
            <atom:updated>2017-11-04T21:11:45.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*EJf1MIFRPIOUd_Rns8Yqiw.png" /></figure><p>ESLint is a tool which helps you to write perfect JavaScript. Now it is easy to install it feature packed with best style configs out there: Airbnb Style Guide + JavaScript Standard Style.</p><p>See <a href="https://github.com/airbnb/javascript">airbnb/javascript</a> and <a href="https://standardjs.com/">standardjs</a> for more information. <a href="https://npmcompare.com/compare/eslint-config-airbnb,standard">Compare</a> configs.</p><p>Just install <a href="https://www.npmjs.com/package/eslint-config-airbnb-standard"><strong>eslint-config-airbnb-standard</strong></a> npm module globally:</p><pre>npm install --global eslint-config-airbnb-standard</pre><p>And now you can use supernormal ESLint from anywhere:</p><pre>eslint -v<br>eslint app.js</pre><p>Don’t forget to create .eslintrc file in your project. Also setup your IDE / Editor to fix your styles on the fly!</p><p>ES6, ES7, React, JSX, async/await — all new features supported by default 👍</p><p>Local installation is also appropriate. Install the module with --save-dev flag and use <strong>npx</strong> tool to run local ESLint: npx eslint -v</p><p>You can also find instructions for <a href="https://www.npmjs.com/package/eslint-config-airbnb-standard#atom"><strong>Atom</strong></a> and <a href="https://www.npmjs.com/package/eslint-config-airbnb-standard#webstorm"><strong>WebStorm</strong></a>.</p><h3>How to use it in Sublime Text 3?</h3><ol><li>Install the package npm i -g eslint-config-airbnb-standard</li><li>Go to: <em>Preferences -&gt; Package Control -&gt; install package</em></li><li>Install <a href="https://packagecontrol.io/packages/SublimeLinter">SublimeLinter</a></li><li>Install <a href="https://packagecontrol.io/packages/SublimeLinter-contrib-eslint">SublimeLinter-contrib-eslint</a></li><li>Run npm bin -g… and copy the path</li><li>Go to: <em>Tools -&gt; SublimeLinter -&gt; Open User Settings</em></li><li>Paste the path (nodejs global bin folder) inside “paths” for your OS, for example:</li></ol><pre>&quot;paths&quot;: {<br>    &quot;linux&quot;: [<br>        &quot;~/.nvm/versions/node/v8.1.2/bin&quot;<br>    ],<br>    &quot;osx&quot;: [],<br>    &quot;windows&quot;: [<br>        &quot;%AppData%\\npm&quot;<br>    ]<br>},</pre><p>8. Create .eslintrc file inside your working project:</p><pre>{<br>  &quot;extends&quot;: [&quot;airbnb-standard&quot;]<br>}</pre><p>9. Restart Sublime Text</p><p>10. Have fun!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZLuOuzpHYhI_MPAN." /><figcaption>Sublime Text 3 linting</figcaption></figure><h3>What if I want to turn off semicolons?</h3><p>You can turn off semicolons in .eslintrc (<em>semi -&gt; &quot;never&quot;</em>) for your project:</p><pre>{<br>  &quot;extends&quot;: [&quot;airbnb-standard&quot;],<br>  &quot;rules&quot;: {<br>    &quot;semi&quot;: [2, &quot;never&quot;],<br>    &quot;object-curly-spacing&quot;: [2, &quot;never&quot;]<br>  }<br>}</pre><p>Good luck on your coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=965a1db58793" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/eslint-with-airbnb-standard-js-sublime-text-965a1db58793">ESLint on steroids with Airbnb + Standard JS styles</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>