**_This_ article** **_originally appeared on_** [**_dormoshe.io_**](https://dormoshe.io/articles/facebooks-prepack-the-next-killer-in-the-javascript-zone-7)

In the last days, the social networks are stormy about **_Prepack_**. Probably you still haven’t heard about it. That’s reasonable! It has been an **open source** only a few days ago. Prepack has developed by Facebook and it is under active development. It’s experimental and still in very early stage, but it is awesome 😱.

In this article, we will introduce Prepack, cover what Facebook wants to solve, see some cool examples and understand the current state of Prepack.

### **Pre.. What?**

> Prepack is a tool that optimizes JavaScript source code

Computations that can be done at **compile-time**, instead of run-time, get **eliminated**. Prepack **replaces the global code of a JavaScript bundle** with equivalent code that is a simple sequence of assignments. This gets rid of most intermediate computations and object allocations.

![](https://pbs.twimg.com/profile_images/762858401390927875/uW_17lxZ_bigger.jpg)

Sebastian McKenzie — one of the Prepack developers

Prepack is a **partial evaluator** for JavaScript. Prepack rewrites a JavaScript bundle, resulting in JavaScript code that executes more efficiently. For initialization-heavy code, Prepack works best in an environment where JavaScript parsing is effectively cached.

#### And What About The Closure Compiler?

> Prepack focuses on runtime performance, while the Closure Compiler emphasizes JavaScript code size.

The Closure Compiler also optimizes JavaScript code. Prepack goes further by truly running the global code that initialization phase, unrolling loops and recursion.

#### A Piece of history

One year ago, at React-Europe 2016 conference, Sebastian McKenzie talked about how making JavaScript initialization faster.

![](https://i.ytimg.com/vi/xbZzahWakGs/hqdefault.jpg)

McKenzie talk at React-Europe 2016

So, now we know more about it. There are name and website and we can use it.

### How To Start?

Prepack shipped as an npm package and you can use it by Prepack-CLI tool or by API calls to the Node.js module.

#### Prepack CLI

In order to install the Prepack-CLI, run

`npm install -g prepack`

And then to compile a file, run

    prepack script.js

#### Prepack API

In order to install in it a project, run

    npm install --save-dev prepack

and then the js code looks like:

![](https://avatars3.githubusercontent.com/u/15105764?v=3&s=400)

Prepack api usage via npm package — code example

#### prepack-webpack-plugin

There is a webpack plugin for using Prepack in a convenient way.

![](https://avatars3.githubusercontent.com/u/15105764?v=3&s=400)

webpack plugin usage example

### Let The Show Begin

Here are some cool examples. The left side in the examples contains the input and the right side contains the output of Prepack.

The first example is a traditional hello world example:

![](https://hackernoon.com/hn-images/1*vquseZscba8gr9LsZCMctQ.png)

Example 1

As you can see, Prepack compiled the code to the smallest version.

The next example contains two functions. Here is the code:

![](https://hackernoon.com/hn-images/1*9_FovuSD9DXADQDh1SS9uQ.png)

Example 2

The compiled code is generated from the first function. Function `func2` is useless and it does not contain any side effect code, so there is no compiled code associated with `func2`.

Pay attention, code that is not in an [IIFE](https://developer.mozilla.org/en-US/docs/Glossary/IIFE) is not a fully optimized.

![](https://hackernoon.com/hn-images/1*FntmE0DuNM0g5Yf2MpeV4Q.png)

Example without IIFE

This example shows coding with a for loop. The loop was removed in the compiled code, but there is a lot of unused lines. With an IIFE it will look like:

![](https://hackernoon.com/hn-images/1*dl-5aQNOhz832INsRnUbrw.png)

Example with IIFE

Here you can see that there are only 5 lines of the log operation.

#### Playground

You can try it out by yourself in a special playground in the Prepack website (see it in the references section). The playground is the better option for those who don’t want to install it or interest just in playing with Prepack.

![](https://hackernoon.com/hn-images/1*HHXhRQJjjAdzpZ1BgL8kQA.png)

Playground example

### Current State

#### **Github Measures**

Prepack code hosted (with ❤️) by Github and published via npm.

![](https://hackernoon.com/hn-images/1*p5V_80C4TjZgJjCnylYbTQ.png)

Github

There are 15 contributors, about ~6500 stars, ~2000 downloads this week via npm and ~130 forks. These statistics are **expected to leap** in the upcoming period since increased interest by developers in the social networks.

There is a funny issue you really want to know about…

[**Converts 1 meaningless line to 1065 lines of code · Issue #543 · facebook/prepack**  
_Looks like @bevacqua managed to break it. Try running this modified example from the docs (function() { function fib…_github.com](https://github.com/facebook/prepack/issues/543 "https://github.com/facebook/prepack/issues/543")[](https://github.com/facebook/prepack/issues/543)

But it is OK. They will fix it in the near future.

#### Tests Coverage

The [code coverage](https://446-45147841-gh.circle-artifacts.com/0/tmp/circle-artifacts.hh6xQWZ/coverage-report-sourcemapped/index.html) report for serialization tests is available to all. Right now the coverage is **52.37%**.

![](https://hackernoon.com/hn-images/1*-cK6NnvSSt8aML94bdYgOw.png)

Code coverage

Prepack’s code coverage generated by [Istanbul](http://istanbul-js.org/).

#### Roadmap 🎯

Facebook has a [**roadmap**](https://prepack.io/) for the development of Prepack. The roadmap is divided into three parts: short, medium and long terms.

In the short term, Facebook wants to stabilize the existing feature set for Prepacking of React Native bundles. They also want to do an integration with React Native toolchain. In addition, they plan to build out optimizations based on assumptions of the module system used by React Native.

The long-term vision is to **leveraging Prepack as a platform.**

### Last Attention

Prepack doesn’t recognize `document` and `window`, so their value will be `undefined`. Therefore, we would have to do some preparations for handling this issue. Maybe someone wants to write some npm package for this purpose? 😇

Facebook asks the developers to try Prepack, give feedback, and help them by bugs fixing and by contribution in the Github repository.

### References

Here are some useful links for further reading:

*   [Github repository](https://github.com/facebook/prepack)
*   [npm package](https://www.npmjs.com/package/prepack)
*   [Official website](https://prepack.io/)
*   Prepack [playground](https://prepack.io/repl.html)

### Conclusion

Prepack can be a “life changer”. It is backed by a stable company — Facebook. They want to integrate this tool in React and they have been worked on that for a while. There are a lot to do. The vision of Facebook is to **leveraging Prepack as a platform**. It sounds promising. I will follow their advance. Prepack is awesome!

![](https://hackernoon.com/hn-images/1*cA1Y2VmIvRnUJUvjUPNZ2A.png)

**_You can follow me on_** [**_dormoshe.io_**](https://www.dormoshe.io) **_or_** [**_Twitter_**](https://twitter.com/DorMoshe) **_to read more about Angular, JavaScript and web development._**

Facebook

Mozilla

Twitter

Too Long; Didn't Read

Cassandra Forward a free Cassandra-focused community event

Facebook’s Prepack — The Next Killer In The JavaScript Zone

Too Long; Didn't Read

Companies Mentioned

@dormoshe

RELATED STORIES