<?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 Even Stensberg on Medium]]></title>
        <description><![CDATA[Stories by Even Stensberg on Medium]]></description>
        <link>https://medium.com/@evenstensberg?source=rss-f3e507726e9d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*KoOgEv8KHqQjNC77sUq2EA.jpeg</url>
            <title>Stories by Even Stensberg on Medium</title>
            <link>https://medium.com/@evenstensberg?source=rss-f3e507726e9d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:43:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@evenstensberg/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[The new webpack Command Line Interface]]></title>
            <link>https://medium.com/@evenstensberg/the-new-webpack-command-line-interface-8dc55d6efa43?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8dc55d6efa43</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Fri, 15 Nov 2019 15:34:30 GMT</pubDate>
            <atom:updated>2019-11-15T15:34:30.208Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GURkSs4itwpPUf9Gzo9Mjg.png" /><figcaption>New interface help screen</figcaption></figure><p>As promised, we’re releasing the new webpack CLI. The Command Line Interface is a change to the previous webpack CLI in many ways and let me go through them in this post.</p><p><strong>This is important, so I want to start this post by saying that this version (v.4) is a breaking change and that you will need to change the way you invoke webpack through webpack CLI. Many flags are being replaced in favor for a more user-friendly Command Line Interface.</strong></p><p><em>The release is done gradually, in order to make sure that the new CLI does not break your current application. We are releasing a beta version where we need feedback to fix bugs that are critical, where we have some months of buffer to help people transition from version 3 to 4.</em></p><h3>Configuration Location</h3><p>We’ve gotten feedback about webpack being hard to configure in addition to webpack not being strict enough on convention. From now on, we’re trying to enforce that webpack configurations should be located in a <em>.webpack </em>folder to keep track of configuration files. This is us following the same convention as git, babel and other tools out in the industry.</p><p>Even though this is recommended for large scale projects, you are still able to have your configuration files at root level just as before, you decide.</p><h3>Environment-based configurations</h3><p>Consider the scenario where you want to run your production or development build. In the current-state you will need to set <strong>NODE_ENV=development|production, </strong>configure your library to use the development or production build, appropriate loaders, source-maps and plugins needs to be tweaked.</p><p>This is a repetitive task, and in addition to having different configurations, you will need to configure a lot of options in order to get your builds <em>just right. </em>We’re trying to make that experience better, we can’t promise to get every build right, but we try to define defaults that make sense on a general basis. As of v4, you are able to have production, development and base configurations that are automatically found, instead of providing the path to a configuration once you set an environment for your build.</p><p>For instance, normally, you would have a traditional production build invoked as following:</p><p>$ NODE_ENV=production webpack — mode=production — config ./webpack.config.prod.js</p><p>In the new CLI, you will be able to run $ webpack --prod and have the same effect. The CLI will be able to detect the production or development configuration and to fill default configuration properties the best it can. In addition, the functionality is used when you want to merge two configurations together in the new flag merge .</p><p>If you do not provide a path to this flag, webpack will try to look for a file webpack.merge.js . If you do decide to provide a filepath, this is done through:</p><p>$ webpack --merge ./my.webpack.config.js .</p><h3>Development Server and Scaffolding Included by Default</h3><p>If you are familiar with the concept of <a href="https://github.com/webpack/webpack-dev-server">webpack-dev-server</a>, the development server will have flags that could be invoked in webpack-cli. The same functionality persists, but in exchange for installing a dev-server, you will now be able to run the development server by invoking webpack serve instead with the flags you wish, if you install webpack-dev-server.</p><p>The strength of this, is to be able to interact with the <strong>webpack </strong>namespace singly instead of having two different namespaces for development (webpack-dev-server and webpack).</p><p>You are able to initialize a new webpack project by running webpack create . You will be asked a series of questions of how you wish to have your project structured and if you would like to create one without worrying, you can create a default project by running webpack create --auto .</p><p><em>Please note that this feature has been disabled in the beta, but will be enabled soon, because the dependency of serve in a monorepo will cause imports in the mono-repo to be wrongly imported when installing the CLI. We are working on fixing this.</em></p><h3>Better Defaults, error handling and warnings</h3><p>As briefly mentioned, we are now setting better defaults. Parts of that is not visible to the user and we are having an aggressive approach to setting those defaults. This is why we have decided to initially have the default being set through a flag --defaults , that you could provide to test the full capabilities of the new CLI.</p><p>The people contributing to the CLI would be very thankful with any feedback on these defaults and in general with the new CLI itself.</p><h3>MJS and Configuration files in other formats</h3><p>You are able to write your configurations in MJS, TypeScript or any other dialect, if you have the dependencies for that installed. For instance, with MJS, you need to install <a href="https://github.com/standard-things/esm">esm</a>. If you get an error when trying to run your configuration in another dialect, install the package webpack is trying to import, but is missing.</p><h3>Feedback</h3><p>In addition to these features, we have refactored the Command Line Interface to make the logic more maintainable, and configurable. The visuals of the Command Line Interface has changed a lot, and we’re curious of any feedback, and more specifically about the following:</p><ol><li>Convention — are we making it easier to have a structured web application?</li><li>Visualization — Is the new CLI more handy to work with? Does having multiple compilations have any drawbacks visually?</li><li>Defaults — Is there anything that is getting overridden and you wish we hadn’t?</li><li>Missing flags — Are there any flags you wish the CLI had or once had, but are now removed?</li><li>MJS Configurations — We are interested in the error handling, and how you use webpack with configurations written in TypeScript, MJS, or other conventions, and any problems you had when trying to do this.</li></ol><h3>Future</h3><p>We are actively trying to make your experience with the CLI better, it takes time. That being said, we are working on a feature set to allow you to benchmark your webpack builds, run performance analysis and to run webpack in an interactive mode (watch mode with full control over webpack stop-start and tweaking).</p><p>Before a stable version is ready, documentation has to be written, and final functionalities of the development server will need to be written.</p><p><strong>If you want to test the new CLI</strong>, you can do so by installing the beta through npm: npm install --save webpack-cli@beta</p><p><strong>That’s all! If you have any feedback, please do not hesitate to reach out to us, we really want to improve the user experience with webpack, and any feedback goes a long way!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dc55d6efa43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Summer of Code Closing Conference]]></title>
            <link>https://medium.com/webpack/google-summer-of-code-closing-conference-60be2d9bd9a2?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/60be2d9bd9a2</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[sustainable-development]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Tue, 22 Oct 2019 12:43:45 GMT</pubDate>
            <atom:updated>2019-10-22T12:43:45.972Z</atom:updated>
            <content:encoded><![CDATA[<p>W(w)ebpack has now been involved in Google Summer of Code for 2 years, and it has been a fantastic opportunity for the organization to help the community evolve, students to get into the Open Source space and help the ecosystem grow and continue to be sustainable.</p><p>This year, two of our Mentors have participated in the closing conference, Google Summer of Code Mentor Summit in Munich, Germany. During the conference, mentors from all organizations met and spoke about important topics that are relevant for every Open Source organization out there. As an organization, it is important to care about the community, ecosystem and how the organization is helping making the Open Source space better, which we do (!a lot!).</p><p>The summit hosted representatives from <a href="https://git-scm.com/">Git</a>, <a href="https://sugarlabs.org/">Sugarlabs</a>, <a href="http://www.freebsd.no/">FreeBSD</a>, <a href="https://www.un.org/en/">UN</a>, <a href="https://metabrainz.org/">MetaBrainz</a>, governments and many other awesome organizations! These representatives provided insight in various of sessions together with other mentors on how we together could help sustainability, the ecosystem both in software and in the world of climate as well.</p><p>During these sessions, discussions about sustainability in projects, pull request review processes and building a healthy community was one of the core values, which was talked about in great depth and by people that care, which from a maintainers perspective, was amazing to be apart of.</p><p>Discussions of Operating Systems and burnout were also on the agenda. All these topics were really important, and from our perspective: Valuable to how we reason about Open Source governance, helping the world progress and thrive.</p><p>After attending this conference, it’s clear that the hardship of Open Source is everyones problem, not just the problems webpack are facing. The community as a whole does an immense job at making tools, libraries and source more available. Seeing so many passionate, smart and inspiring people communicate, collaborate and work together has been an eye-opener for us, and there is no doubt that the ecosystem is in the best hands, maintained by the most genuine people.</p><p>As mentors this year, we appreciate the work put into from students and other people that continues to make webpack better over time, day by day. This project is driven by the community, which is the way Open Source should be run. Thank you for this years students that made an incredible effort into their projects, <a href="https://summerofcode.withgoogle.com/archive/2019/projects/4895317185527808/">making code cleaner</a> and <a href="https://summerofcode.withgoogle.com/archive/2019/projects/4597762119696384/">reporting better</a>! Finally, thank you to all other contributors that continues to put in the effort to make the web better. A few people I want to thank, is Alexander Krasnoyarov, <a href="https://twitter.com/EugeneHlushko">Eugene Hlushko</a> and <a href="https://twitter.com/ematipico">Emanuele Stoppa</a>.</p><p>Thanks to all new contributors, welcome at any time to contribute to webpack, existing ones that aren’t mentioned, but still do tremendous efforts, thank you!!</p><p>Below is a few pictures we took during the conference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VDAGngKHlCzGUuKLV6A0sw.png" /><figcaption>[Photo booth] webpack representing at GSOC2019</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNt2m9pxdoKEJrrQgS7POA.png" /><figcaption>[Photo booth picture ]In Open Source you wear many hats</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1jW0bn54VlCxpbTrwVzFdA.png" /><figcaption>[Group Photo] A group photo with other mentors!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-tzZc9fczIdkTA35dCHMxA.png" /><figcaption>[Group Photo] webpack and <a href="https://sugarlabs.org/">sugarlabs</a> ❤</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HdiwqtNt7SzikBDE0eK5-w.jpeg" /><figcaption>[Even and Steven pictured during the conference] We’re not actually into this, but it was a good picture! :)</figcaption></figure><p>Thanks to everyone involved, organizers and attendees, it was a great event and we thank everyone for having a safe and inclusive community that genuinely cares about the future of Open Source!</p><p>If you are <a href="https://summerofcode.withgoogle.com/how-it-works/">interested in participating as a student</a> for webpack during Google of Code or you want to contribute to webpack, please do reach out to us, we would love to get you started! ♥</p><p>Our mentors, maintainers and contributors are friendly, we do not bite. You can contact us through twitter at our <a href="https://twitter.com/webpack">individual handles</a>.</p><p>Again, thank you for an eye-opening experience!</p><p>Even Stensberg &amp; Steven Hargrove</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60be2d9bd9a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webpack/google-summer-of-code-closing-conference-60be2d9bd9a2">Google Summer of Code Closing Conference</a> was originally published in <a href="https://medium.com/webpack">webpack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On building communities..]]></title>
            <link>https://medium.com/@evenstensberg/on-building-communities-a15cff27322b?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a15cff27322b</guid>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Thu, 16 May 2019 02:26:10 GMT</pubDate>
            <atom:updated>2019-05-16T02:26:10.336Z</atom:updated>
            <content:encoded><![CDATA[<p>Initially I didn’t want to write about such a vague topic, but I think it is important to flesh out some thoughts about how to build a community for an open source project.</p><p>In December 2016 I got involved in webpack. Webpack is a fairly large project and is used by <em>almost </em>everyone in the front end community. When we first started with webpack CLI, I had no idea of how to properly do Open Source. I was still in high school and enjoyed exploring software.</p><p>The change from developing applications to being responsible of how people build applications were huge. I was ambitious (still am), and had no idea what I was involved in.</p><p>As for most Open Source projects out there, getting new contributors might be hard, so it is important to be transparent enough for people to be able to contribute, and I think we’ve done that well.</p><p>Our initial team started fleshing out a scaffolding tool, which will help new users create projects easier, and it quickly became a big task. Later on, we found out that this was too much to maintain, which would make the effectiveness of maintaining webpack-cli harder. As time went, people get out of OSS for various of reasons, kids, school, work and so on. As a maintainer, it is hard to do everything on your own and I think I share the same opinion about this along with a lot of other maintainers out there.</p><p>After a period in 2017 the CLI team was very small and we had no real traction other than being able to help people with issues and moving slowly towards a better experience for people using webpack. We then decided we needed to spent time not actually only fixing bugs, but also to get people involved in the project so we had a better time maintaining webpack. That choice turnt out to be great, not only for the organization itself, but also for a healthy relationship to the community. What I mean by that, is that we were able to tackle bigger tasks, have more people to oversee code written and more input on decisions that was about to be made.In hindsight, for me, it was crazy to think about having the responsibility of the tool that runs roughly speaking the entire modern web today without having a team large enough to provide critical thinking and feedback.</p><p>A lot of positive things start to arise once you build a community around your project, which, for instance could be more people helping you, people getting experience after contributing and you will also open career opportunities for others.</p><p>In 2018 webpack participated for the first time in Google Summer of Code, an internship arranged by Google for students to work on Open Source projects. We are doing this in 2019 and it has shown not only to be a great way to improve a project, but also a way for people to get work experience, crucial for a student.</p><p><strong>Build a community, spread knowledge and celebrate transparency.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a15cff27322b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Front End Applications with Deno]]></title>
            <link>https://medium.com/@evenstensberg/building-front-end-applications-with-deno-b42f47b5ddef?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b42f47b5ddef</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[deno]]></category>
            <category><![CDATA[rust]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Wed, 10 Apr 2019 17:50:18 GMT</pubDate>
            <atom:updated>2019-04-10T17:50:18.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Nq1fQSPq9aeoWxn4WFbhg.png" /><figcaption>This is a nodeJS logo</figcaption></figure><p><em>I recently stumbled into </em><a href="https://deno.land/"><em>Deno</em></a><em>, which is a typescript runtime for something something blockchain ai.</em></p><p><strong>Thing is</strong>, Deno is great, because it doesn’t leave a node_modules folder in your application, so you’ll have a better time maintaining stuff. It’s still flaky at some points, and there’s some aspects of it which isn’t quite done.</p><p>The current trend in web right now is also directed towards having less dependencies visible in your root folder and storing complexity or dependencies somewhere. This is great, and developers will have a better time maintaining stuff.</p><p>I started with experimenting with having a simple TCP server that would get a response and I’d answer with static web page. Simple enough.</p><p>Deno is great as an isolated server instance, but porting existing dependencies might take a while and people aren’t quite sold on the good parts Deno provides. Anyways, so I was hacking away and there was some complications, not big, but still makes your head banging a bit.</p><p>Deno doesn’t support CJS format in imports, as this is a Rust isolated instance with the V8 sandbox made by Google, sprinkled with TypeScript on top, it’s hard to import already present front end solutions such as React and Preact into your Deno app.</p><p>Now why would I use React and these deps in Deno? My primary goal was to emit zero bundles to anything on disk and serve everything on the go, like you want your coffee. Secondly, Deno provides TypeScript out of the box, so creating a new React application would simply be done by having a</p><p>$ deno ./index.js and you would have access to both JavaScript &amp; TypeScript. Best of two worlds.</p><p>Lastly, I’m procrastinating.</p><p>To start this project, I went ahead and imported Preact from unpkg ( a CDN provider), it turns out, as I’ve briefly explained here, that Deno doesn’t like CJS files, so I tried to find a MJS CDN for Preact (MJS and Deno works great by the way, let’s use MJS in NodeJS, don’t @me). I found the CDN, and it was all honey and ice until I wanted to render actual React/Preact components with Deno.</p><p>I thought: Hmm, I’m hungry, so I ate. After that I went ahead and started working on a solution to build front-end applications with Deno using JS and without having to rewrite any modules. Deno is a runtime, so it’s hard. However, we can do dynamic import injection (read a file, parse it and import the actual module). We’re gonna do this because regular JS modules doesn’t suffice, we need to transform CJS modules that are used in front-end to ES6 modules.</p><p>Thing is, we already got a tool that does the trick for us, webpack. However, webpack is written in CJS so we need to convert that into ES6 first. After that is done, one could run webpack in memory, which in turn compiles files in memory, which in turn will not output any files locally, but emit them in memory. Then, you will be able to serve un-allocated files in your local TCP server without actually emitting anything to disk. Neat, right?</p><p>You will also be able to develop without setting up transpilation because of the nature of Deno.</p><p>I’ve started some work on this, which you can find here:</p><ul><li><a href="https://github.com/evenstensberg/deno-webpack">evenstensberg/deno-webpack</a></li><li><a href="https://github.com/evenstensberg/require-to-deno">evenstensberg/require-to-deno</a></li><li><a href="https://github.com/denoland/deno/issues/2091">Polyfilling `require` · Issue #2091 · denoland/deno</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b42f47b5ddef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing a solid Google Summer of Code Proposal]]></title>
            <link>https://medium.com/@evenstensberg/writing-a-solid-google-summer-of-code-proposal-a200fc6e785b?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a200fc6e785b</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Sat, 09 Mar 2019 17:12:40 GMT</pubDate>
            <atom:updated>2019-03-09T17:12:40.216Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QmkV3qgiCWmF_-wc496syg.png" /><figcaption>Google Summer of Code</figcaption></figure><p>I’m apart of webpack, an organization that participated in Google Summer of Code in 2018 and this year (2019). In this post, I’ll share some tips on how to write a proposal that will increase your chances getting accepted. As a mentor I’ve been reviewing a lot of proposals and this is a summary of best practises.</p><h3>Introduction</h3><p>What are you applying to work on? What is the organization doing and what does the project you want to contribute to do? This is where you elaborate on a higher level what the project is.</p><p>After doing a short introduction of the organization and the project you want to contribute to, start with an introduction of your idea. What makes your proposal want us to accept you? What makes it unique?</p><h4>Keywords:</h4><ul><li>Give a brief outline of the organization and project</li><li>Elaborate your idea and what makes it good</li></ul><h3>Description</h3><p>This is probably the longest and most important section of your proposal. In the previous section, you’ve highlighted your idea, this is the section where you provide an overview of how to solve the problem.</p><p>Start with explaining the problem space and the problem you are trying to solve. After doing so, you will elaborate on how you intend to solve the problem. A non-technical anecdote is not enough. You will need to come up with a layout that explains the solution at a technical level, without going too deep.</p><p>A tips for writing these kinds of texts, is to discuss the problem as it was a select company listening what you are saying and asking you questions about problems that might arrive. Remember to split up your solution into multiple sub-sections.</p><h4>Keywords:</h4><ul><li>Explain the problem</li><li>Write a technical solution</li><li>Explain your approach in depth and write it reflectively</li></ul><h3>Timeline</h3><p>What’s your schedule? How will you come through with your proposal? Explain how you will dedicate your time during the summer to submit deliverables. This section is important, because it will be the reference to your deliverables this summer. GSoC has several phases and make sure that you write a table or an overview of what you will be doing during these phases.</p><h4>For instance:</h4><p><strong>Phase 1: 28–29th of February</strong>:</p><ul><li>x is implemented</li><li>y is fixed</li><li>z is zappy</li></ul><p>These phases are evaluated by mentors and they will use your proposal as a reference to determine if you are passing or not. Do you have anything to mention that we need to know about? Are you going on holidays? How much time are you planning to use each day or week? Planning and letting the mentors know will be in your favor.</p><blockquote>It does not do to leave a live dragon out of your calculations, if you live near him.</blockquote><blockquote>~J.K Tolkien, The Hobbit</blockquote><p><strong>Important phases to mention</strong>:</p><p>May 6–27— Community bonding</p><p>May 27-June 24th,— Phase 1</p><p>June 28th-July 24th— Phase 2</p><p>July 24th-August 19th — Phase 3</p><h4>Keywords:</h4><ul><li>Plan your proposal</li><li>Explain what you will be doing during phases</li></ul><h3>Experience</h3><p>If you have contributed to the project or organization before, that is a positive thing. If so, mention how you contributed as it will show that you are motivated and know how to contribute to the project.</p><p>In this section you should write about yourself, a little like a resume but keep it relevant. Include personalia, experience, OSS experience (none is ok, that’s a reason for applying), work experience and relevant information. If you do not have much experience, a tip is to give us some examples of projects you’ve done at school and how you solved them.</p><h4>Keywords:</h4><ul><li>Who are you? Write about yourself</li><li>Show us that you are qualified</li><li>Mention relevant OSS experience or related</li></ul><h3>Few Remarks</h3><ul><li>Start early with your proposal</li><li>Try to contribute to the organization, it has positive effect</li><li>Talk to mentors, ask for feedback</li><li>Don’t be afraid to come up with your own ideas or features you want to work on, but mention it before writing the official proposal so mentors can give feedback</li><li>Work hard, don’t be lazy, but have fun while doing Google Summer of Code :)</li></ul><h3>Example Structure</h3><ul><li>Introduction</li><li>Problem Space</li><li>Proposal Description</li><li>Schedule/Timeline</li><li>Experience/About Me</li></ul><h3>Summary</h3><p>I hope this guide has helped you getting a feel of how a proposal is structured. This is not the recipe though, you can shape your proposal as you’d like as long as it is thorough and it contains relevant information. Think of it like a university report or a science report. Feel free to reach out to me if you have any questions, happy to help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a200fc6e785b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First Meaningful Paint: When page content finally shows up to the party]]></title>
            <link>https://medium.com/@evenstensberg/first-meaningful-paint-when-page-content-finally-shows-up-to-the-party-4ef8a3e37daf?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ef8a3e37daf</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Fri, 22 Feb 2019 17:32:18 GMT</pubDate>
            <atom:updated>2019-02-22T17:32:18.966Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYpp9LdEO5mx7XYabFswDA.jpeg" /><figcaption>Painting is a nice way to get ideas to life</figcaption></figure><p><strong>First meaningful paint or more often referred to FMP is a key metric in web performance. It’s important because it tells us more about how the general user perceives your website. In 2014 the average website sent 75 requests, so let’s focus on one thing and see what we can do there.</strong></p><h4>Asynchronous Loading &amp; non-blocking rendering</h4><p>Asynchronous Loading and non-blocking rendering is all about loading files on-demand. This means that your first priority is always to make the website look interactable, followed up with functionality efforts. Most of modern websites today are using some sort of build tool, either if it is gulp, parcel or webpack. The good thing about these tools is that they often provide these mechanisms out of the box for you.</p><p>Async loading is a way to omit loading a module or a JavaScript file until it is really needed. <a href="https://webpack.js.org/guides/lazy-loading/">Have a look at the webpack documentation as an example of how this is achieveable.</a> As Google developers has a nice tutorial about just this theme, I’ll give you two other resources to check out:</p><ul><li><a href="https://developers.google.com/web/fundamentals/performance/critical-rendering-path/">Critical Rendering Path | Web Fundamentals | Google Developers</a></li><li><a href="https://bitsofco.de/understanding-the-critical-rendering-path/">Understanding the Critical Rendering Path</a></li></ul><h3><strong>Lighthouse</strong></h3><p>Lighthouse is a tool designed to analyze your webpage and its metrics. It will give you some indications of what you did right and what you did wrong so you could have a chance to improve your websites’ performance and loading time. You should check it out.</p><p><a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse | Tools for Web Developers | Google Developers</a></p><h3>Conclusion</h3><p>Performance is important but hard to master. Use lighthouse to monitor your page and try to find out where your application bottleneck is. WebpageTest is also a tool you could use to audit your application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ef8a3e37daf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apache and PHP with OCI8 + Oracle Instant Client in Mac OSX]]></title>
            <link>https://medium.com/@evenstensberg/apache-and-php-with-oci8-oracle-instant-client-in-mac-osx-100343970159?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/100343970159</guid>
            <category><![CDATA[apache]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[oci8]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[instant-client]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Fri, 22 Feb 2019 17:26:57 GMT</pubDate>
            <atom:updated>2019-02-22T17:26:57.208Z</atom:updated>
            <content:encoded><![CDATA[<h3>Configuring Apache and PHP with OCI8 + Oracle Instant Client in Mac OSX</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHg9OvYDTSOLs86KCwviCw.jpeg" /><figcaption>I’m running a 13&#39;’ MacBook Pro v.10.13.6 ( High Sierra ).</figcaption></figure><p>After spending some time in Apache trying to configure OCI8, I quickly concluded that it is a pain to configure. This post will go through how to get any OCI and Instant Client up and running on your Mac OSX.</p><h3>Prerequisites</h3><ul><li>You have PHP installed on your Mac ( v.7.x is the latest, but anything is fine)</li><li>You have knowledge of what a symlink is</li><li>You can read</li></ul><h3>Getting started</h3><h4>PHP</h4><p>Before actually doing anything, I’m making sure that I have PHP installed at the correct path and that thephp.initfile is located somewhere I know.</p><p><strong>$ php — version</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VmSi3xw76x5JV0gU3XEPg.png" /><figcaption>I’m running PHP version 7.2.6</figcaption></figure><p><strong>$ which php</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9X46VCTDGtYMnIIEqNBnyA.png" /><figcaption>php is under /usr/local/bin</figcaption></figure><p><strong>$ php — ini</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LInDicJKTJPH3kJ9efruGQ.png" /><figcaption>Our configuration file for php is under usr/local/etc/php/7.2</figcaption></figure><p>The reason why we are looking for this file is because this is where our OCI8 module will get included in order for PHP and Apache to detect the dependency and to use it. If you don’t have the file located, you can create one by doing touch /etc/php/is/located/here/php.ini . If you are wondering what your PHP path is, you can do which php . The easiest way to install PHP is via <a href="https://brew.sh/">Homebrew</a> if you don’t already have that installed.</p><h4>Instant Client</h4><p>Instant Client is what OCI8 depends on in order to run successfully. We will have to install Instant Client from the <a href="https://www.oracle.com/technetwork/topics/intel-macsoft-096467.html">Official Oracle site</a>, and you might need to create a user.</p><h3>Install The Following:</h3><ul><li><a href="https://www.oracle.com/technetwork/topics/intel-macsoft-096467.html">instantclient-basic-macos.x64–12.2.0.1.0–2.zip</a> (This depends on which release is the latest, but this is mine)</li><li><a href="https://www.oracle.com/technetwork/topics/intel-macsoft-096467.html">instantclient-sdk-macos.x64–12.2.0.1.0–2.zip</a> (This depends on which release is the latest, but this is mine)</li><li>Additionally you can install sqlplus to verify that your symlinks are correct after we’ve installed these dependencies.</li></ul><p>After these have been Downloaded, navigate to where you have downloaded them. My downloads are located at/Users/ev1stensberg/Downloads/instantclient-x-macos.x64.</p><p>Now we are ready to link the dependencies to OSX to be able to use their commands to make them function as regular Command Line Applications. Before doing that, we need to unpack the zip files at a given location.</p><p>From experience, to avoid denied permissions from the system and forgetting the location of where the folder is located, I tend to extract these files under /opt/somewhere .</p><p><strong>We begin </strong>by creating a folder for our directory for zip extraction:</p><p>$ mkdir -p /opt/oracle</p><p><strong>Secondly </strong>we move the downloaded folders to the <em>oracle</em> folder</p><p>$ mv /Users/ev1stensberg/Downloads/instantclient-basic-macos.x64-12.2.0.1.0-2.zip /opt/oracle</p><p>$ mv /Users/ev1stensberg/Downloads/instantclient-sdk-macos.x64-12.2.0.1.0-2.zip /opt/oracle</p><p><strong>Third </strong>is to unzip the files we have moved to the oracle folder</p><p>$ unzip /opt/oracle/instantclient-basic-macos.x64-12.2.0.1.0-2.zip</p><p>$ unzip /opt/oracle/instantclient-sdk-macos.x64-12.2.0.1.0-2.zip</p><p><em>Optional: </em><strong><em>Now as we have unzipped the files to the oracle folder, you can safely remove the zip files from the folder by doing</em></strong>$ rm -rf /opt/oracle/*.zip <strong><em>.</em></strong></p><p><strong><em>If you failed at the third step, don’t worry. You can move and unzip the files via </em></strong>finder<strong><em>.</em></strong></p><h3>Integrating Instant Client To OSX</h3><p>Now we are ready to actually use the programs we have installed. In order to do so, we will have to create symlinks to /usr/bin in order for the mac to treat the files as executables, such as the cd or ls command.</p><p><strong>You</strong> can do so by doing:</p><pre>$ sudo ln -s /opt/oracle/sdk/include/*.h /usr/local/include/<br>$ sudo ln -s /opt/oracle/*.dylib /usr/local/lib/<br>$ sudo ln -s /opt/oracle/*.dylib.11.1 /usr/local/lib/<br>$ sudo ln -s /opt/oracle/libclntsh.dylib.11.1 /usr/local/lib/libclntsh.dylib</pre><p>You can’t really verify the command you are doing if you aren’t symlinking <em>sqlplus</em> as well. You can also <a href="https://gist.github.com/krisanalfa/09b765bb95012cd36fbd#preparation">look at this guide</a>, to try another approach. In this example we are creating a soft symlink to our mac’s /usr/local folder, which will make the mac pick up the library as a global executeable.</p><p>Next up is to install OCI8, which is a hard nut to crack. I’m going to show you the hard way to link OCI8 because the <a href="https://gist.github.com/krisanalfa/09b765bb95012cd36fbd#install-extension-with-pecl">pecl</a> way of doing it is quite buggy.</p><h3>Installing and linking OCI8</h3><p>When trying to install oci8, it might be productive to check if the extention is loaded. To check if oci8 is enabled, you can add the line <em>dd(extension_loaded(‘oci8’)); </em>to your entry php file (mine is<em> index.php</em>)</p><p>You will need to install OCI8 from source as the package manager sometimes is hard to reason about. First, find your <a href="https://pecl.php.net/package/oci8">oci8 download link</a>, and navigate to the downloaded folder.</p><p>This part is tricky, because Pecl, the PHP package manager usually extracts the package for us and runs the installation with symlinks. First, we start by extracting the tar (zipped) file into a destination:</p><pre>$ tar -zxf oci8-x.x.x.tgz<br>$ cd oci8-x.x.x</pre><p>After doing so we need to prepare the package meta-data by using phpize . If you are having troubles, you will need to spend some time debugging why the command might fail, but here are some links:</p><ul><li><a href="https://stackoverflow.com/questions/8430977/phpize-wont-work-on-mac-os-x-lion">phpize won&#39;t work on Mac OS X Lion</a></li><li><a href="https://xdebug.org/docs/install">Installation</a></li></ul><p><a href="http://php.net/manual/en/install.pecl.phpize.php">http://php.net/manual/en/install.pecl.phpize.php</a></p><p>If your command works, run: phpize inside the un-extracted directory.</p><p>Now is the time to install OCI8, and you can run the following command:</p><pre>$ ./configure --with-oci8=shared,instantclient,/path/to/instant/client/lib</pre><p>$ make install</p><p>If you have troubles with installing this at any point, I advice you to install OCI8 through PECL and then follow along whichever script PECL is running. Reproduce those steps manually and fix the issues the build steps have.</p><p><strong>Congrats! You’re done!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=100343970159" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architectural Beams in Front End]]></title>
            <link>https://medium.com/@evenstensberg/architectural-beams-in-front-end-f85160e3306b?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f85160e3306b</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Fri, 22 Feb 2019 17:00:38 GMT</pubDate>
            <atom:updated>2019-02-22T17:00:38.216Z</atom:updated>
            <content:encoded><![CDATA[<p>Every now and then a new post about how to work with a stack, regardless of library is published. Having done a lot of work in React, there seems to be few posts that cover a well defined architecture.</p><p>Front End projects are unique in a way, because unlike many back-end systems and legacy front-end libraries and frameworks, we can reuse more modules of code. In an abstract level, this is essentially what happens in module bundlers as well. We recognize those modules the same, and glue them together to spit out chunks of code that are optimized for our application, which again makes the user experience better in effect of faster parse and load time on webpages.</p><p>Architectural wise, we can relate to this with a different perspective. When we build a front-end project with reusability and user experience in mind, we can come up with a clean structure which is easy to navigate around. This is reflected in terms of developer experience.</p><p>There is all kinds of combinations to a well defined project structure and how you choose to structure a Front End application built with React is dependent on which condition your project is in. Before expanding on that thought, let us define a good baseline for a traditional React application.</p><p>We start by creating a minimum project with React and webpack. For a clean top-tier structure, I like to have all webpack configurations under one folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMv-R2IfufWsDn-8x_-aHQ.png" /></figure><p>For different environments, a fairly standardized convention is to suffix your files with the environment and use those configurations for the given npm command, such as npm run prod . This gives developers headspace so that they do not need to navigate through the entire webpack configuration to know which part is configured for a given environment.</p><p>At this point, the most important part is how you are going to structure the React application. I prefer a top-level folder named lib although src works just as fine.</p><p>Inside lib is where the important sections are. To make a project readable and maintainable, it is important to make clear separations of concerns. For instance, if you have a REST-API, it is smart to put the Http calls inside their own respective folders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2OeDcrVlgtYpWmGvfikWA.png" /></figure><p>This setup makes your view (React) cleaner to work with instead of embedding REST-API code in your view folders.</p><p>Next up is React. Depending on which phase your project is in, a technique that has worked well in many of projects I’ve been involved in, is to split logic based on different types of services your application offers, or to split based on the types of users your application has. This is up to you, if the users have the same layout, it might be better to split logic based on services you provide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZPmSWkL3Do_e4uXK6e6eIQ.png" /></figure><p>In this example, your project could have a codename, as well as you might have different stacks on different parts of your application. As seen in the picture above, we split the architecture based on the services that a given application might have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jt7nZEWjtGLD_zUFQ1KGKg.png" /></figure><p>In each of these service folders, we have a 2 folder — 1 file layout. Containers are responsible for fetching and handling data, sending them down to components. This way, a divide between visualizing data and handling data is provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apWCFEzeRFLWdYXX6dHAsQ.png" /></figure><p>For styling, I like to have styles locally for each component so that each component is isolated and it is easy to navigate and edit design without having to use time on global stylesheets. Another variant, is to have a flat style structure, but it will not scale well once there are a lot of components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6qZZbJGaQ4mcnl-XIcw79Q.png" /></figure><p>In the utils folder, normally one just has the pure JavaScript functions/helpers that are needed across the application. This might seem smart, but in reality when developing a product there are a lot of situations where your project is a bit noisy, and a good middleway to strike then, is to put your common react components in this folder and abstract it to a private npm package or styleguide later. You can also remove it and move it closer to the folders using it the most (incommon/utils folders) later.</p><h3>Why is a strict folder structure really needed?</h3><p>Once you are in the wind and your application has gone through some development, it is more normal to produce code on top of your existing stack instead of having to refactor code to incrementally improve your application.</p><p>When the Egyptians built pyramids they didn’t remove two bricks to move the structure, they used blocks to stack up the structure. In this case, you do not usually move big files and re-arrange them every time you do a Pull Request. In that case your team members would think you’re insane doing so.</p><p>Instead, developers tend to:</p><p>A) Live with a well defined architecture and build layers on top of a solid foundation</p><p>B) Develop a unmaintainable until they get depressed and quit, followed up by another developer hopefully starting to refactor the code</p><p>The ideal case would be A. Since the market is heavily based on shipping code and making things work, it is obvious that you will need to start with a fresh slate and then build your way up to complexity. In the end, you will save more money as a business, doing the work properly and then focusing on being fast, then rushing to market with an unbearable codebase.</p><p>And there are more aspects to this argument, which will often be proved empirically. As a newly hired developer you might get thrown straight into the frying pan without any knowledge of a battlefield of pitfalls. These pitfalls usually are centered around “getting started”, “getting up and running” and so on.</p><p>I disagree on that part. Why? It’s a developers job to make the source code easy to navigate around, easy to start and a developer should never be concerned with not being able to do his/hers job because the infrastructure is too much of a headache to get by with.</p><p>The contradiction to a well defined structure is clear as opposed to the winning arguments, which is, loosing talent and building a strong engineering team. From a managers perspective, it might be hard to see the profit in investing time making your code look neat opposed to making money, but making money is an in-direct effect of how a developer can use time focusing on development. In this case, maintainability.</p><h3>Too many bugs in your bed? Replace it, don’t fix it</h3><p>I’ve been working in the industry for a couple of years now and also with the tooling that drives the industry, and I’ve seen some tendencies towards a bug being a singular case where one thing goes wrong cause the issue is obviously isolated and only occurs this one time and nowhere else. From an analyst perspective, you know that these incidents aren’t really unique but they share a common trait. Once you see more bugs of the same start grouping, the finite solution is to fix the way the system works, not monkey patching an issue since the stack is being replaced somewhere soon anyway.</p><p>You, as a developer will save yourself tons of hours debugging, working around quirks and delaying timelines because of this. The problem isn’t the isolated instance, but the un-encapsulated structure of it.</p><p>This case is also related to performance , believe it or not. It is unfortunate that we do not have metrics on well-defined structures in applications to those who aren’t, my hypothesis is that we will see the well-defined ones are more performant than those who are smaller in features. Why? It’s a prioritization problem. Larger apps have more work, sure, but they also have the advantage of a well designed architecture.</p><h3>Conclusion</h3><p>If you are building an application, do it properly. Define well defaults and make up a good structure for it before starting. It will yield great results in length and even if your traction isn’t big to start with, it will have a longer lifetime than a short-term solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f85160e3306b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with Open Source — Tricks of the trade]]></title>
            <link>https://medium.com/@evenstensberg/getting-started-with-open-source-tricks-of-the-trade-d5a42b41349d?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5a42b41349d</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Thu, 27 Dec 2018 00:57:10 GMT</pubDate>
            <atom:updated>2018-12-27T00:57:10.995Z</atom:updated>
            <content:encoded><![CDATA[<h3>Getting started with Open Source — Tricks of the trade</h3><p>Getting into Open Source is hard, and there might be many reasons for it. To try to make this easier, this post will go through a few tricks of the trade that will make it easier to contribute, get started and to benefit from Open Source.</p><p>One of the most popular platforms that host source code online, is <a href="http://github.com/">GitHub</a>. If you are unfamiliar with GitHub, it is smart to create an account. After creating an account, a great guide explaining how to navigate around can be found <a href="https://guides.github.com/activities/hello-world/">here</a>.</p><p>It would be smart to know programming before actually starting to contribute to Open Source, but it’s not required. Most of the time, you can actually learn and become a better programmer by doing Open Source.</p><p>Before starting any coding or related, it’s important that you find out which language you can help out with, which will make it easier to find an issue to solve. If you do not want to contribute to coding, don’t worry, <a href="https://opensource.guide/">there are other ways to help</a>!</p><p>One of the things I like to use when finding out which project to contribute to, is to search for a repository that is not too hard, the correct language and has issues that are approachable. For that, GitHub has a nice search feature that can help you out.</p><p><a href="https://github.com/search/advanced">Build software better, together</a></p><p>A little tip when starting is to narrow search down by filtering from 0–1000 stars, “Help Wanted” or “Good First Contribution” labels and to find contact a maintainer of a promising issue, asking them for help, if needed.</p><p>Other than that, it’s about asking for help, finding mentors, ask questions and browsing through issues, finding something to do! I have created a<a href="https://github.com/evenstensberg/getting-started-with-open-source/issues/2"> repository</a> for first timers that will serve as a nice starter and will be available for mentoring until 2019 starts.</p><p>I’ve gathered some links that you might find useful:</p><ul><li><a href="https://github.com/search/advanced">https://github.com/search/advanced</a></li><li><a href="https://www.firsttimersonly.com/">https://www.firsttimersonly.com/</a></li><li><a href="https://hackernoon.com/yet-another-journey-of-contributing-to-open-source-6443077b204f">https://hackernoon.com/yet-another-journey-of-contributing-to-open-source-6443077b204f</a></li><li><a href="https://rubygarage.org/blog/how-contribute-to-open-source-projects">https://rubygarage.org/blog/how-contribute-to-open-source-projects</a></li><li><a href="https://www.quora.com/How-do-I-start-contributing-in-Open-Source-projects">https://www.quora.com/How-do-I-start-contributing-in-Open-Source-projects</a></li><li><a href="https://medium.freecodecamp.org/how-to-make-your-first-open-source-contribution-in-just-5-minutes-aaad1fc59c9a">https://medium.freecodecamp.org/how-to-make-your-first-open-source-contribution-in-just-5-minutes-aaad1fc59c9a</a></li><li><a href="https://www.codetriage.com/">https://www.codetriage.com/</a></li><li><a href="https://www.hackerearth.com/getstarted-opensource/">https://www.hackerearth.com/getstarted-opensource/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5a42b41349d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We are changing the interface of webpack-cli — here’s why]]></title>
            <link>https://medium.com/webpack/we-are-changing-the-interface-of-webpack-cli-heres-why-2e8057f2eda1?source=rss-f3e507726e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e8057f2eda1</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Even Stensberg]]></dc:creator>
            <pubDate>Fri, 07 Dec 2018 14:15:21 GMT</pubDate>
            <atom:updated>2018-12-07T14:15:21.838Z</atom:updated>
            <content:encoded><![CDATA[<h3>We are changing the interface of webpack-cli — here’s why</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6g60YCnJk7fz9V7ztzpkbg.jpeg" /><figcaption>Let’s make development smooth as waves</figcaption></figure><p>Every now and then we hear people make jokes about configuration being hard. It’s true, and webpack hasn’t been the most trivial tool to use when getting into web development.</p><p><strong>That’s why we are changing</strong> the interface and webpack. When doing this, we are making the CLI of webpack better to look at, simpler to use and easier for users to understand.</p><p><strong>With this goal in mind</strong>, we are confident that users will spend less time setting up the tool itself, to spending more time doing the fun part, actually developing the application. We do not want users to give up on web development once encountering webpack, rather we want to encourage people to have less configuration when starting and then making more advanced builds as they develop a traditional web application.</p><p><strong>One of the best search results </strong>from google had the word “<em>beginners guide</em>” in it, which indicates that we have made a bad job at making the CLI of webpack easy to use.</p><p><strong><em>We are sorry…</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*a_2nOnu-hemLLFuAXhopXw.png" /><figcaption>Norwegian words and some english</figcaption></figure><p><strong>Ives Van Hoorne</strong>, the creator of CodeSandBox made this great illustration of how development feels like. It makes sense, because we want the user to use less time figuring out how things work to have more time developing an application. As webpack itself is a tool that is flexible, we do not need to make a web application perfect at once, but rather over time and by setting good default values for users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*7RKbG5vMNbkiUG4l4PdUzQ.png" /></figure><p><strong>Webpack-CLI </strong>will try to set the best defaults for you, meaning that we will optimize your build as much as we can, making it easier for you to have a fast application with no configuration. We are also making it easier for users to start different kinds of configurations such as React, SAAS or similar. This will allow you as a user to run webpack-cli without having to specify anything. The good stuff.</p><h3>Removing flags</h3><p><strong>In the newest version of webpack-cli</strong>, we will remove a lot of specific flags that we think is too advanced to be in the CLI. We encourage users to write specific logic for their builds through a webpack configuration rather than writing a one-liner with 1337 characters.</p><p><strong>The result of this is</strong> that the new CLI will be cleaner, provide more clarity to new users, the output will (finally) be more prettier, less rubbish in the output of a compilation and we will set good defaults.</p><p><strong>Good defaults</strong> in this case would be that you will have performance optimizations out of the box, loading styles, files are easier based on your current project structure as well as development and production flags will be improved.</p><h3>Adding Flags</h3><p><strong>We will add a few new flags</strong> to make debugging and developing in watch mode easier,<strong> webpack-ui </strong>is going to be released later in v4, a <strong>merge flag</strong> to merge two configurations together will be added and finally, <strong>node flags</strong> are going to be supported.</p><p><strong>Webpack-UI will be released</strong> along with a command/flag named <em>webpack interactive</em>. These two flags are targeted for helping new users understand webpack in a graphical way, to debug webpack interactively and provider a more convenient platform to run webpack from rather than from the Command Line Interface.</p><p><strong>The changes are coming</strong> in the upcoming webpack-cli version, version 4.0.0 and it will be released in alpha by the end of December. We will release the CLI in a slow matter, to ensure that people reliant on the old CLI flag, will have backwards compatibility. A more detailed post along with proper documentation of how to migrate your application will be published soon as we release the alpha version for you to test and experiment with.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e8057f2eda1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webpack/we-are-changing-the-interface-of-webpack-cli-heres-why-2e8057f2eda1">We are changing the interface of webpack-cli — here’s why</a> was originally published in <a href="https://medium.com/webpack">webpack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>