<?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[Smooth Code - Medium]]></title>
        <description><![CDATA[JavaScript trainings for developers in Paris and around the world. - Medium]]></description>
        <link>https://medium.com/smooth-code?source=rss----10e6f84a36de---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Smooth Code - Medium</title>
            <link>https://medium.com/smooth-code?source=rss----10e6f84a36de---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:17:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/smooth-code" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing Smooth UI System, a new way to style components]]></title>
            <link>https://medium.com/smooth-code/introducing-smooth-ui-system-a-new-way-to-style-components-7125b0312f85?source=rss----10e6f84a36de---4</link>
            <guid isPermaLink="false">https://medium.com/p/7125b0312f85</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[styled-components]]></category>
            <category><![CDATA[css-in-js]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Bergé Greg]]></dc:creator>
            <pubDate>Fri, 08 Mar 2019 08:55:40 GMT</pubDate>
            <atom:updated>2019-03-08T09:15:42.828Z</atom:updated>
            <content:encoded><![CDATA[<p>We are proud to share with you Smooth UI’s brand new « <strong>System</strong> »: a fresh way to <strong>create styled components</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f0eMLx2tRYEM9GzP" /><figcaption>Photo by <a href="https://unsplash.com/@salvoventura?utm_source=medium&amp;utm_medium=referral">salvatore ventura</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Smooth UI</h3><p>A year ago, I published the first version of <a href="https://smooth-ui.smooth-code.com/"><strong>Smooth UI</strong></a>, a generic design system to help us build React applications at <a href="https://www.smooth-code.com/"><strong>Smooth Code</strong></a>. Today Smooth UI has more than 1K stars, is widely used and powers dozen of websites.</p><p>Smooth UI is a simple UI library focused on developer productivity. It exposes primitives only: a <strong>powerful grid</strong>, <strong>responsive utilities</strong>, base components and — of course — a <strong>powerful styling system</strong>.</p><h3>What is the system?</h3><p>System is the core of Smooth UI. It exposes useful style utilities that you can use directly in props. Today we introduce a new way to use the system, a new way to create components, a new style syntax.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/336ba5681b9d5117afe650692882d0c2/href">https://medium.com/media/336ba5681b9d5117afe650692882d0c2/href</a></iframe><p>What does this example mean? A lot of things:</p><ul><li>A background with color “primary”</li><li>A width of 100% on mobile, 50% on desktop</li><li>A height of 100px</li><li>A padding of 16px</li><li>A marginLeft and a marginRight of 50%</li></ul><p>This small example shows the power of the system, it is only a subset of <a href="https://smooth-ui.smooth-code.com/docs-system-utilities">all available utilities</a>. In fact, the list is CSS reference itself because all CSS properties are supported.</p><p>The system can also be used directly on properties, this way you can style the components in a declarative way, right from your JSX code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a47e84c012888bd3426158786c454409/href">https://medium.com/media/a47e84c012888bd3426158786c454409/href</a></iframe><p>In the above example, the Box is a simple div infused with Smooth UI system. It means you can use all system properties as props.</p><p>I prepared a Code Sandbox, feel free to play with it:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fm4x4ww81j9&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fm4x4ww81j9&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fm4x4ww81j9%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/07f2ee638d767b92ce971e570c00ee28/href">https://medium.com/media/07f2ee638d767b92ce971e570c00ee28/href</a></iframe><h3>Benefits of the system</h3><p>So why use this system instead of writing plain CSS? Why should I use another pseudo CSS language?</p><h4>Developer experience</h4><p>As a developer, the less you write, the more effective you are. The system reduces the amount of code to write. For example, usep instead ofpadding , m instead of margin , an object instead of a complex media query. At the end of the day all these small utilities represent a huge gain of time.</p><h4>Design Consistency</h4><p>The system reads values from your theme, so wherever you need a color, you can use “primary”, “secondary” or whatever name you choose. Your entire app is configured right from your theme.</p><p>This is even more true for spaces. You can use your own unit to defined them. When I typep={1} , it will use the padding unit define in your theme, by default it is 8px but you are free to choose the one you decide. You don’t have to worry about pixels anymore, they just think in terms of unit. And if you want to condense your design, you only have to reduce the unit in the theme.</p><p>And it is a game changer for responsive. Responsive breakpoints are configured from the theme, you don’t have to worry about it anymore.</p><h4>Flexbility</h4><p>Being able to style a component right from props is very convenient. Most of the time you want to add a margin on a component. Being able to add simple prop my={1} is awesome. It is like discovering Prettier, it gives you real power, simplicity and flexiblity.</p><h3>Conclusion</h3><p>At Smooth Code, we use the system every day and it is a real game changer for us. That is why I wanted to share with the community our way to create components. And yes it is open source and fully documented.</p><p><a href="https://smooth-ui.smooth-code.com/docs-system-getting-started">Smooth UI</a></p><p>I would be happy to have your insights and see what you are going to build with it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7125b0312f85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smooth-code/introducing-smooth-ui-system-a-new-way-to-style-components-7125b0312f85">Introducing Smooth UI System, a new way to style components</a> was originally published in <a href="https://medium.com/smooth-code">Smooth Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to deploy Ghost v1.x on Heroku]]></title>
            <link>https://medium.com/smooth-code/how-to-deploy-ghost-v1-x-on-heroku-56ad26633eb0?source=rss----10e6f84a36de---4</link>
            <guid isPermaLink="false">https://medium.com/p/56ad26633eb0</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[ghost-v1]]></category>
            <category><![CDATA[ghost-blog]]></category>
            <category><![CDATA[ghosts]]></category>
            <dc:creator><![CDATA[Bergé Greg]]></dc:creator>
            <pubDate>Mon, 28 Aug 2017 14:46:56 GMT</pubDate>
            <atom:updated>2017-08-29T18:39:40.707Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to deploy Ghost v1.x on Heroku for free</h3><p>Ghost is a very popular blog platform that supports Markdown. It is very powerful and easy to use. This article will give you the keys to deploy it quickly and for free on Heroku.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*DAqHaGvQbDxJhjOWmuETTw.png" /><figcaption>The Ghost blog platform logo.</figcaption></figure><h3>1. Create a new application on Heroku</h3><p>The first step is signing up for Heroku. If you are familiar with Heroku, just go to the next step, else you can follow this <a href="https://devcenter.heroku.com/articles/quickstart">quick start guide</a>.</p><h3>2. Downloading Ghost</h3><p>As I am writing this article, the last version of Ghost is v1.7.1.</p><ul><li><a href="https://ghost.org/developers/">Head to the website and download the last version</a>.</li><li>Unzip the Ghost version in the directory of your choice:</li></ul><pre>$ unzip ~/Downloads/Ghost-1.7.1.zip -d ~/projects/my-blog<br>$ cd ~/projects/my-blog</pre><h3>3. Create a Heroku application</h3><p>Since Heroku deployment is based on git, we have to create a git repository to host Ghost source code.</p><p>To initialize a new git repository, use these commands in your project directory:</p><pre>$ git init<br>$ git add -A<br>$ git commit -m &#39;Initialize repository&#39;</pre><p>Next we will set-up the application using heroku-cli. If you do not have heroku-cli installed on your machine, follow this guide: <a href="https://devcenter.heroku.com/articles/heroku-cli">https://devcenter.heroku.com/articles/heroku-cli</a>.</p><p>First we create an application, replace “my-blog” by the name of your blog.</p><pre>$ heroku create my-blog</pre><pre>Creating ⬢ my-blog... done<br><a href="https://nzo-blog.herokuapp.com/">https://my-blog.herokuapp.com/</a> | <a href="https://git.heroku.com/nzo-blog.git">https://git.heroku.com/my-blog.git</a></pre><p>We can now deploy our blog on Heroku.</p><pre>$ git push heroku master</pre><pre>Released v13<br><a href="https://nzo-blog.herokuapp.com/">https://my-blog.herokuapp.com/</a> deployed to Heroku</pre><p>Even if the deployment was successful, your blog is not functional yet. A major element is still missing: the database.</p><h3>4. Install mySQL</h3><p>Ghost database is mySQL, to make it work on Heroku, you have to choose a mySQL provider. I am not an expert but ClearDB sounds like a good choice. Let’s add the mySQL add-on to our application:</p><pre>$ heroku addons:create cleardb:ignite</pre><pre>Creating cleardb:ignite on ⬢ my-blog... free<br>Created cleardb-aerodynamic-72322 as CLEARDB_DATABASE_URL<br>Use heroku addons:docs cleardb to view documentation</pre><p>The add-on is now installed but it is still not used by our Ghost application. We must set up database credentials using heroku config:</p><p>First, get credentials of your database:</p><pre>$ heroku config:get CLEARDB_DATABASE_URL</pre><pre>mysql://b74638b58e8fff:<a href="/service/mailto:dc933939@us-cdbr-iron-east-05.cleardb.net">dc944939@us-cdbr-iron-east-05.cleardb.net</a>/heroku_6a6045b8e83395b?reconnect=true</pre><p>You should get something like that, the format of the url is : “mysql://user:password@host/database?reconnect=true”</p><p>Second, using heroku config:set, configure each part of the url:</p><pre>$ heroku config:set \<br>database__connection__user=b74638b58e8fff \<br>database__connection__password=<a href="/service/mailto:dc933939@us-cdbr-iron-east-05.cleardb.net">dc944939</a> \<br>database__connection__host=<a href="/service/mailto:dc933939@us-cdbr-iron-east-05.cleardb.net">us-cdbr-iron-east-05.cleardb.net</a> \<br>database__connection__database=heroku_6a6045b8e83395b</pre><pre>Setting database__connection__user, database__connection__password, database__connection__host, database__connection__database and restarting ⬢ my-blog... done, v4<br>database__connection__database: heroku_6a6045b8e83395b<br>database__connection__host:     <a href="/service/mailto:dc933939@us-cdbr-iron-east-05.cleardb.net">us-cdbr-iron-east-05.cleardb.net</a><br>database__connection__password: <a href="/service/mailto:dc933939@us-cdbr-iron-east-05.cleardb.net">dc944939</a><br>database__connection__user:     b74638b58e8fff</pre><p>Unfortunately the free tier of ClearDB does not allow us a lot of connections. We can set the connections to 2 max, enough for a small website:</p><pre>$ heroku config:set database__pool__max=2</pre><p>You database connection is now configured, but database is still empty. We must initialize it using heroku run.</p><pre>$ heroku run &quot;knex-migrator init&quot;</pre><pre>Running knex-migrator init on ⬢ my-blog... up, run.3926 (Free)<br>[2017-08-28 13:47:59] INFO Creating table: posts<br>[2017-08-28 13:47:59] INFO Creating table: users<br>[2017-08-28 13:47:59] INFO Creating table: roles<br>[2017-08-28 13:47:59] INFO Creating table: roles_users<br>[2017-08-28 13:47:59] INFO Creating table: permissions<br>[2017-08-28 13:47:59] INFO Creating table: permissions_users<br>[2017-08-28 13:47:59] INFO Creating table: permissions_roles<br>[2017-08-28 13:47:59] INFO Creating table: permissions_apps<br>[2017-08-28 13:48:00] INFO Creating table: settings<br>[2017-08-28 13:48:00] INFO Creating table: tags<br>[2017-08-28 13:48:00] INFO Creating table: posts_tags<br>[2017-08-28 13:48:00] INFO Creating table: apps<br>[2017-08-28 13:48:00] INFO Creating table: app_settings<br>[2017-08-28 13:48:00] INFO Creating table: app_fields<br>[2017-08-28 13:48:00] INFO Creating table: clients<br>[2017-08-28 13:48:00] INFO Creating table: client_trusted_domains<br>[2017-08-28 13:48:00] INFO Creating table: accesstokens<br>[2017-08-28 13:48:00] INFO Creating table: refreshtokens<br>[2017-08-28 13:48:00] INFO Creating table: subscribers<br>[2017-08-28 13:48:00] INFO Creating table: invites<br>[2017-08-28 13:48:01] INFO Creating table: brute<br>[2017-08-28 13:48:01] INFO Model: Post<br>[2017-08-28 13:48:01] INFO Model: Tag<br>[2017-08-28 13:48:01] INFO Model: Client<br>[2017-08-28 13:48:02] INFO Model: Role<br>[2017-08-28 13:48:02] INFO Model: Permission<br>[2017-08-28 13:48:03] INFO Model: User<br>[2017-08-28 13:48:03] INFO Relation: Role to Permission<br>[2017-08-28 13:48:04] INFO Relation: Post to Tag<br>[2017-08-28 13:48:04] INFO Relation: User to Role<br>[2017-08-28 13:48:04] INFO Finished database init!</pre><p>If you see “Finished database init!” it is good. Do not panic if command is not responding. Just terminate it manually (control + C).</p><h3>5. Configure server</h3><p>We have to change the host binding, the default is “127.0.0.1” but using Heroku we have to set it to “0.0.0.0”.</p><pre>$ heroku config:set server__host=0.0.0.0</pre><p>We can also set up our blog url:</p><pre>$ heroku config:set url=https://my-blog.herokuapp.com</pre><p>On Heroku, the web application port is dynamic and provided in “PORT” environment variable by Heroku.</p><p>In Ghost, we have to set up the application port using “server__port” environment variable.</p><p>To make an alias between “PORT” and “server__port” we create a “.profile” at the root of our application.</p><pre>$ echo &quot;export server__port=\$PORT npm start&quot; &gt; .profile<br>$ git add .profile<br>$ git commit -m &#39;Add .profile&#39;<br>$ git push heroku master</pre><p>Your blog is now ready, enjoy!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56ad26633eb0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smooth-code/how-to-deploy-ghost-v1-x-on-heroku-56ad26633eb0">How to deploy Ghost v1.x on Heroku</a> was originally published in <a href="https://medium.com/smooth-code">Smooth Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing loadable-components ✂️✨]]></title>
            <link>https://medium.com/smooth-code/introducing-loadable-components-%EF%B8%8F-646dd3ab0aa6?source=rss----10e6f84a36de---4</link>
            <guid isPermaLink="false">https://medium.com/p/646dd3ab0aa6</guid>
            <category><![CDATA[webpack-2]]></category>
            <category><![CDATA[react-router]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[code-splitting]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Bergé Greg]]></dc:creator>
            <pubDate>Mon, 26 Jun 2017 14:23:29 GMT</pubDate>
            <atom:updated>2017-06-26T14:23:29.316Z</atom:updated>
            <content:encoded><![CDATA[<p>A library to solve React code splitting client-side and server-side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Opa0cpg3l-mwD8Iq4jy6MQ.png" /><figcaption>Thanks styled-components for inspiration (for your logo and your simplicity).</figcaption></figure><h3>Introduction</h3><p>If you are familiar with <strong>React ecosystem</strong> (Babel, Webpack, ES6…), you have probably already heard of <strong>code splitting</strong>. Code splitting means dividing your code into small pieces called “chunks” to reduce the size of bundle loaded by user. Reducing the size of a chunk makes it load and run faster. Amazon said it better <a href="https://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales"><em>“1 sec could cost $1.6 Billion”</em></a>. Web performance is a feature, not a fix, if you can make your website faster, you should do it.</p><h3>Webpack</h3><p>Webpack has been supporting <a href="https://webpack.js.org/guides/code-splitting-async/">on-demand code splitting</a> for a while and Webpack 2 has introduced <a href="https://github.com/tc39/proposal-dynamic-import"><strong>dynamic-import</strong></a> support. This is a new specification <a href="https://github.com/tc39/proposals"><strong>currently in stage 3 of TC39 process</strong></a>. Using import() is the best way to split your code.</p><p>An example of basic code splitting:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fbd73ca7c7d355610cdb3bfec3f40a84/href">https://medium.com/media/fbd73ca7c7d355610cdb3bfec3f40a84/href</a></iframe><p>Running webpack main.js output.js on the previous example will result in two files: the first, output.js containing main.js and a.js, the second output.0.js containing b.js.</p><h3>React</h3><p>Most of the time you are using <a href="https://github.com/ReactTraining/react-router">react-router</a> to manage your React application. — If you are not doing so, your application is probably small and does not require code splitting. — <strong>The best way, we found out, to split your application is by route.</strong> Why? Because routes can be easily loaded asynchronously without degrading the user’s experience since they expect a little wait after clicking on a link.</p><p>If you are using the version 4 of react-router, your code looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e5d525fbb1ca8043145239bce6cde98/href">https://medium.com/media/1e5d525fbb1ca8043145239bce6cde98/href</a></iframe><p>In this example, Home, About and Topics components are <strong>loaded synchronously.</strong> This means that <strong>Webpack will not put them in different chunks</strong>. The goal is to load them <strong>asynchronously</strong> using import().</p><p>To do this is to wrap your component then load it on mount:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d273aeb4352d30f739d79e7f7ad256c1/href">https://medium.com/media/d273aeb4352d30f739d79e7f7ad256c1/href</a></iframe><p>As you can see it’s very simple but you don’t want to have to write that everywhere. <strong>loadable-components</strong> can do it for you, this is exactly the goal of loadable() function. It wraps your components into an async component loaded at mount:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7c7d288ab46ee4a63da54c7a74c8c3e0/href">https://medium.com/media/7c7d288ab46ee4a63da54c7a74c8c3e0/href</a></iframe><p>All your routes are now loaded asynchronously and will be splitted by Webpack, pretty easy isn’t it? 😌</p><p>This is the simple case, with no loading or error support, if you need it you can refer to <a href="https://github.com/smooth-code/loadable-components">the documentation of loadable-components</a>.</p><h3>Server-side rendering</h3><p>At this point you are probably thinking: “I’ve already read it ten times, the problem is not there!”. Yes, you are right, the real problem with code splitting is to make it work with server-side rendering. And providing a solution to this is the goal of <strong>loadable-components</strong>.</p><p>Server-side, you do not have any Webpack. It is node and node does not currently support dynamic imports. You have two choices:</p><ul><li><a href="https://webpack.js.org/configuration/target/#components/sidebar/sidebar.jsx">Building your code with Webpack targetting node</a></li><li>Transpiling it using <a href="https://github.com/airbnb/babel-plugin-dynamic-import-node">babel-plugin-dynamic-import-node</a></li></ul><p>Whatever your choice, it is the same, we just need to make import() work in a Node.js environment.</p><h4>Rendering the application server-side</h4><p>The first problem you will face is rendering your application. React renders an application synchronously, you cannot say <em>“Hey, wait for my component please!”</em>. All components have to be loaded before. The difficulty is that you do not have any idea of what components are required before rendering the application. <strong>You have to load modules before rendering the application but you also have to render the application to know what modules are needed.</strong></p><p><a href="http://dev.apollodata.com/">Apollo</a> is a <a href="http://graphql.org/">GraphQL</a> client, it fetches asynchronous data from the server. Server-side they have exactly the same problem. <strong>They have to load data before rendering the application but they also have to render the application to know what data are needed. </strong>They solved it in an elegant way: <strong>traversing the React tree</strong>. The solution is pretty simple, we go over all components and collect required modules. If you are curious about how it works, you should take <a href="https://github.com/smooth-code/loadable-components/blob/master/src/server/index.js">a look at the tree traversing code</a>.</p><p>I tried to implement it with the simplest possible API:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8860423fda0187bde3e892f37f996821/href">https://medium.com/media/8860423fda0187bde3e892f37f996821/href</a></iframe><p>getLoadableState traverses the React tree and loads all needed modules before rendering the application.</p><h4>Load components client-side</h4><p>At this point it works, but you have two problems:</p><ul><li>Client-side you will see a blink because the client loads modules asynchronously even if the server has rendered it</li><li>There is a mismatch between client and server, the client-side rendered code does not contain asynchronous modules</li></ul><p>To resolve this problem, <strong>loadable-components</strong> does two things:</p><ul><li>It collects modules loaded server-side during the tree traversing</li><li>It transfers these id to the client and loads modules before rendering the application</li></ul><p>Again it is easy to implement:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a579a4e538288e370013d1b94b00c60b/href">https://medium.com/media/a579a4e538288e370013d1b94b00c60b/href</a></iframe><p>As you can see, it collects a <strong>state containing modules ids</strong> loaded during tree traversing. Then the state is transferred to the client in a global variable. I got inspired by styled-components for the getScriptTag and the getStyleElement API.</p><p>Finally, client-side, we have to load components found in the state before rendering our application:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c263f157780846443e542ae9c3cc901/href">https://medium.com/media/0c263f157780846443e542ae9c3cc901/href</a></iframe><p>You now have an application working with <strong>code-splitting</strong> and <strong>server-side rendering</strong>.</p><p>Happy code splitting! I hope you enjoy <a href="https://github.com/smooth-code/loadable-components">loadable-components</a> ✂️✨!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=646dd3ab0aa6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smooth-code/introducing-loadable-components-%EF%B8%8F-646dd3ab0aa6">Introducing loadable-components ✂️✨</a> was originally published in <a href="https://medium.com/smooth-code">Smooth Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>