<?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 Louis ⚓ on Medium]]></title>
        <description><![CDATA[Stories by Louis ⚓ on Medium]]></description>
        <link>https://medium.com/@vdclouis?source=rss-1030cc511a6c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*46fYx4GMk6OIy8Mk4RqoHw.jpeg</url>
            <title>Stories by Louis ⚓ on Medium</title>
            <link>https://medium.com/@vdclouis?source=rss-1030cc511a6c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:41:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vdclouis/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[How and why we replaced bower with npm]]></title>
            <link>https://medium.com/@vdclouis/how-and-why-we-replaced-bower-with-npm-da2514346739?source=rss-1030cc511a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/da2514346739</guid>
            <category><![CDATA[bower]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Louis ⚓]]></dc:creator>
            <pubDate>Fri, 04 Dec 2015 08:35:50 GMT</pubDate>
            <atom:updated>2015-12-04T11:02:58.740Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="http://www.showpad.com/">Showpad</a> we have been using <a href="http://bower.io/">bower</a> for years now. In the beginning we were super excited to have a package manager for frontend libraries.</p><p>Then the build tool explosion came along and we used <a href="https://www.npmjs.com/">npm</a> to manage all the plugins we were using to generate production ready code.</p><p>Which in turn got us thinking… Wouldn’t it be nice to have one package manager to rule all modules?</p><p>The decision was quite easy and we went with npm. Especially now that <a href="http://blog.npmjs.org/post/122450408965/npm-weekly-20-npm-3-is-here-ish">npm3</a> is out in the wild (yay flat tree!).</p><p>So, how would we manage the transition? Because, let’s be honest, bower is quite easy to use. After some tinkering I came up with the following solution:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f52f84a08581ddf25780f0ab5eca70d4/href">https://medium.com/media/f52f84a08581ddf25780f0ab5eca70d4/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9b9709ea3ab09c0e8bd4bb1b76a93544/href">https://medium.com/media/9b9709ea3ab09c0e8bd4bb1b76a93544/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2074749233ddd8f8871214e236dddd16/href">https://medium.com/media/2074749233ddd8f8871214e236dddd16/href</a></iframe><p>And there you have it. Clean and simple.<br>As you probably noticed we are using rollup. Rollup is a fairly new module bundler with a lot of potential. We chose <a href="http://rollupjs.org/">rollup</a> over <a href="http://browserify.org/">browserify</a> for a couple of reasons:<br>1. the modules we use are just plain javascript; so no CommonJS<br>2. it feels nice to use the Ecmascript standard<br>3. smaller bundle in the end</p><blockquote>I roll up, I roll up, I roll up, Shawty I roll up<br>I roll up, I roll up, I roll up — <a href="https://www.youtube.com/watch?v=UhQz-0QVmQ0">Wiz Khalifa</a></blockquote><p>As for now we don’t use any <a href="http://requirejs.org/docs/commonjs.html">CommonJS</a> powered modules. But if that is your thing, you can easily extend the gulp task to use a <a href="https://github.com/rollup/rollup-plugin-commonjs">rollup plugin</a> that handles CommonJS. Or use our good ol’ friend, browserify.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da2514346739" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>