<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Commonjs on Minko Gechev&#39;s blog</title>
		<link>https://blog.mgechev.com/tags/commonjs/</link>
		<description>Recent content in Commonjs on Minko Gechev&#39;s blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 21 Jul 2016 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.mgechev.com/tags/commonjs/feed.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>2.5X Smaller Angular 2 Applications with Google Closure Compiler</title>
				<link>https://blog.mgechev.com/2016/07/21/even-smaller-angular2-applications-closure-tree-shaking/</link>
				<pubDate>Thu, 21 Jul 2016 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2016/07/21/even-smaller-angular2-applications-closure-tree-shaking/</guid>
				<description>&lt;p&gt;In the post &amp;ldquo;&lt;a href=&#34;https://blog.mgechev.com/2016/06/26/tree-shaking-angular2-production-build-rollup-javascript/&#34;&gt;Building an Angular 2 Application for Production&lt;/a&gt;&amp;rdquo; we explored how we can decrease the bundle size of a &amp;ldquo;Hello world!&amp;rdquo; application to from about 1.6M (non-minified &amp;amp; uncompressed) to 49K! We did this by using the following techniques:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Angular offline template compiler for generating tree-shakable code.&lt;/li&gt;&#xA;&lt;li&gt;Tree-shaking of ES2015 modules with rollup.&lt;/li&gt;&#xA;&lt;li&gt;Bundling of the application.&lt;/li&gt;&#xA;&lt;li&gt;Minification with uglifyjs.&lt;/li&gt;&#xA;&lt;li&gt;Compression with gzip.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Although we achieved impressive results we can do even better! In this post I&amp;rsquo;ll show some of the work done by &lt;a href=&#34;https://twitter.com/Jakeherringbone&#34;&gt;Alex Eagle&lt;/a&gt; and &lt;a href=&#34;https://twitter.com/jeffbcross&#34;&gt;Jeff Cross&lt;/a&gt; from the Angular core team.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Building an Angular Application for Production</title>
				<link>https://blog.mgechev.com/2016/06/26/tree-shaking-angular2-production-build-rollup-javascript/</link>
				<pubDate>Sun, 26 Jun 2016 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2016/06/26/tree-shaking-angular2-production-build-rollup-javascript/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://developers.google.com/web/progressive-web-apps/&#34;&gt;Progressive Web Applications&lt;/a&gt; help us build native-like web apps, thanks to amazing tools such as Service Workers, IndexDB, App Shell etc. Once the browser downloads all the static assets required by our app, the active Service Worker can cache them locally.&lt;/p&gt;&#xA;&lt;p&gt;This way the user may experience slowdown during the initial page load, but each next time she opens the application her experience will be instant!&lt;/p&gt;&#xA;&lt;p&gt;In order to help developers take advantage of the technologies behind the PWA as easy as possible, the Angular team is working on the Angular &lt;a href=&#34;https://github.com/angular/mobile-toolkit&#34;&gt;mobile-toolkit&lt;/a&gt;. However, a big concern for developing high-performance Angular apps is the framework size itself. For instance, a simple &lt;strong&gt;non-optimized&lt;/strong&gt; &amp;ldquo;Hello world!&amp;rdquo; Angular application, bundled with &lt;a href=&#34;http://browserify.org/&#34;&gt;browserify&lt;/a&gt; is 1.4MB! This is suicidal when your users are supposed to download it via an unreliable 3G connection.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
