A JavaScript bundle optimizer.
Go to file
Dominic Gannaway bf0ed59174 Re-design of the buildNode logic for AbstractValue and GeneratorEntries (#2296)
Summary:
Release notes: much of the buildNode and inline Babel logic has been moved to a dedicated ResidualOperationSerializer class

Note: this PR is like *phase 1* of many phases to move around buildNodes and their logic. Furthermore, the ideas is to move all Babel coupled logic to the serialization phase and away from the generator and other generic areas. I've explained this more in detail below.

This PR moves much of the Babel logic involving build nodes, that was coupled to inline closures through many parts of the Prepack code base, to its own class `ResidualOperationSerializer`. We now use a helper function `createOperationDescriptor` to create `OperationDescriptor`s. `OperationDescriptor`s exist on both `AbstractValue` and `GeneratorEntry`, and replaces the old `buildNode` and `_buildNode` properties and unifies all the logic. The `buildNode` field has now changed to `operationDescriptor` respectfully.

We now have a `OperationDescriptorType` enum that tells the class which build node to use, along with some associated data that is needed to construct the build node (previously this data was captured in the closure). The idea is to remove the data/kind arguments from `createOperationDescriptor` in follow up PRs, but that will take quite a bit more work, thus why this is a phase 1 PR.

In many cases, we now have no instances of importing Babel in many of the files and this unifies much (but not all) of the Babel node creation logic into a single file – allowing for easy extension in the future.

This PR took forever to do and is very large, so there might be bits that I missed, but hopefully I haven't. All tests etc pass locally.
Pull Request resolved: https://github.com/facebook/prepack/pull/2296

Differential Revision: D8923889

Pulled By: trueadm

fbshipit-source-id: aa3a27efd97f10cc941159735d598199deb24f52
2018-07-19 15:41:15 -07:00
.circleci Use Flow server for local development (#2245) 2018-07-18 06:40:25 -07:00
assets Adding raw Prepack Logo assets (#2189) 2018-07-03 12:45:47 -07:00
bin Cleanup files 2017-12-12 11:12:24 -08:00
fb-www Make React tests fast (#2187) 2018-07-02 11:25:58 -07:00
flow-libs Set up adapter communication channel with Prepack 2017-10-27 12:54:08 -07:00
flow-typed/npm Upgrade Prepack to Babel 7 (#2256) 2018-07-14 09:55:18 -07:00
scripts Add serializer mode for test262 execution (#2290) 2018-07-18 18:54:51 -07:00
src Re-design of the buildNode logic for AbstractValue and GeneratorEntries (#2296) 2018-07-19 15:41:15 -07:00
test Don't emit modified bindings unless they are alive (#2287) 2018-07-18 14:40:05 -07:00
website Delete node-cli Option and all the Node.js intrinsics (#2267) 2018-07-16 13:09:59 -07:00
.eslintignore Upgrade Prepack to Babel 7 (#2256) 2018-07-14 09:55:18 -07:00
.eslintrc Prettier 1.13.4 fixes 2018-06-06 12:49:59 -07:00
.flowconfig Use Flow server for local development (#2245) 2018-07-18 06:40:25 -07:00
.gitignore Optimize ReactEquivalenceSet (#2243) 2018-07-13 13:40:00 -07:00
.gitmodules Initial commit 2017-03-28 20:52:41 -07:00
.prettierrc Run Prettier checks on CI (#2212) 2018-07-10 09:55:23 -07:00
.watchmanconfig Add React functional component folding 2017-11-06 05:07:36 -08:00
babel.config.js Add serializer mode for test262 execution (#2290) 2018-07-18 18:54:51 -07:00
CODE_OF_CONDUCT.md Updated the code of conduct links. (#2284) 2018-07-18 10:39:53 -07:00
CONTRIBUTING.md Updated the code of conduct links. (#2284) 2018-07-18 10:39:53 -07:00
LICENSE Initial commit 2017-03-28 20:52:41 -07:00
package.json Bump version for next alpha 2018-07-18 07:24:17 -07:00
PATENTS Initial commit 2017-03-28 20:52:41 -07:00
README.md Adding raw Prepack Logo assets (#2189) 2018-07-03 12:45:47 -07:00
webpack.config.js Upgrade Prepack to Babel 7 (#2256) 2018-07-14 09:55:18 -07:00
yarn.lock Upgrade Prepack to Babel 7 (#2256) 2018-07-14 09:55:18 -07:00

Prepack Circle CI

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.

See the official prepack.io website for an introduction and an interactive REPL playground.

How to use Prepack

Install the CLI via npm,

$ npm install -g prepack

Or if you prefer yarn, make sure you get yarn first,

$ npm install -g yarn

and then install the Prepack CLI via yarn:

$ yarn global add prepack

You may need to prepend (pun intended!) the command with sudo in some cases.

Let the party begin

To compile a file and print the output to the console:

$ prepack script.js

If you want to compile a file and output to another file:

$ prepack script.js --out script-processed.js

Detailed instructions and the API can be found at Prepack CLI: Getting Started

Plugins to other tools

The following are a few plugins to other tools. They have been created and are maintained separately from Prepack itself. If you run into any issues with those plugins, please ask the plugin maintainers for support.

Status

How to get the code

  1. Clone repository and make it your current directory.
  2. git submodule init
  3. git submodule update --init
  4. Get yarn and node, then do yarn

Note: For development work you really need yarn, as many scripts require it.

How to build, lint, type check

  1. Get the code
  2. yarn build
    You can later run yarn watch in the background to just compile changed files on the fly.
  3. yarn lint
  4. yarn flow

How to run tests

  1. Get the code
  2. Make sure the code is built, either by running yarn build or yarn watch
  3. yarn test

You can run individual test suites as follows:

  • yarn test-serializer
    This tests the interpreter and serializer. All tests should pass.
  • yarn test-test262
    This tests conformance against the test262 suite. Not all will pass, increasing conformance is work in progress.

How to run the interpreter

  1. Get the code
  2. Make sure the code is built, either by running yarn build or yarn watch
  3. yarn repl
    This starts an interactive interpreter session.

How to run Prepack

  1. Get the code

  2. Make sure the code is built, either by running yarn build or yarn watch.

  3. Have a JavaScript file handy that you want to prepack, for example:
    echo "function hello() { return 'hello'; } function world() { return 'world'; } s = hello() + ' ' + world();" >/tmp/sample.js

  4. cat /tmp/sample.js | yarn prepack-cli
    Try --help for more options.

How to validate changes

Instead of building, linting, type checking, testing separately, the following does everything together:
yarn validate

How to edit the website

The content for prepack.io resides in the website directory of this repository. To make changes, submit a pull request, just like for any code changes.

In order to run the website locally at localhost:8000:

  1. Build prepack into the website: yarn build && mv prepack.min.js website/js
  2. Run python -m SimpleHTTPServer (Python 2) or python -m http.server (Python 3) from the website/ directory

How to contribute

To read more about the project, check out this suggested reading wiki

For more information about contributing pull requests and issues, see our Contribution Guidelines.

License

Prepack is BSD-licensed. We also provide an additional patent grant.