A JavaScript bundle optimizer.
Go to file
Dominic Gannaway 06736f0df5 Rearchitect evaluatePure and side-effect tracking (#2587)
Summary:
Release notes: the side-effect detection system within pure scopes has been improved

This PR revamps the entire `evaluatePure` system. The old system had so many small issues with it was the cause of many edge-cases that were hard to patch up. Specifically, the PR makes the following changes:

- `realm.evaluatePure` -> `realm.evaluateWithPureScope` and now can only be used a single instance. Nesting further `realm.evaluateWithPureScope` calls will trigger an invariant and is strictly forbidden. Furthermore, it now only takes a single argument – the function you're wrapped around.
- All places that used pure scope wrappers have been updated to conditionally enable it depending if the `realm.isInPureScope()` returns `true` or `false`.
- `realm.evaluateFunctionForPureEffects` has been added, this works like `evaluateForEffects` except it requires a root function and a callback for side-effects. The callback for side-effects works like the old callback that was `evaluatePure`.
- `realm.evaluateFunctionForPureEffectsInGlobalEnv` has been added a convenience wrapper around `realm.evaluateFunctionForPureEffects`.
- When we leak bindings, we no longer set their value to `undefined` or `realm.intrinsics.undefined`. We now set the value to a special "leaked abstract", specifically – `realm.intrinsics.__leakedValue` – like `topValue` and `bottomValue`.

Unsurprisingly, this now fixes a host of bugs that existed before. Including fixes for https://github.com/facebook/prepack/issues/2598, https://github.com/facebook/prepack/issues/2579, https://github.com/facebook/prepack/issues/2446, https://github.com/facebook/prepack/issues/2599 and probably many other issues too.

The logic for detection of side-effects works very differently from before but after speaking to sebmarkbage last week, he pointed me in this direction to track side-effects rather than how we did it before. We now find side-effects from a given set of effects, rather than in an ad-hoc manor as mutations occur on objects/bindings. This PR requires https://github.com/facebook/prepack/pull/2596 as a dependency as it re-uses the logic.

Closes https://github.com/facebook/prepack/pull/2587. Fixes https://github.com/facebook/prepack/issues/2598. Fixes https://github.com/facebook/prepack/issues/2579. Fixes https://github.com/facebook/prepack/issues/2446. Fixes https://github.com/facebook/prepack/issues/2599.
Pull Request resolved: https://github.com/facebook/prepack/pull/2600

Differential Revision: D10368159

Pulled By: trueadm

fbshipit-source-id: ded248f5cfd8648913cae9b9c697d723a82c59ab
2018-10-12 15:45:50 -07:00
.circleci Re-land typed descriptors and printer (#2511) 2018-08-31 05:54:23 -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 Substitute v8-profiler with v8-profiler-node8 (#2525) 2018-09-07 16:39:23 -07:00
fuzzer Fuzzer (#2374) 2018-08-09 10:39:23 -07:00
scripts Rearchitect evaluatePure and side-effect tracking (#2587) 2018-10-12 15:45:50 -07:00
src Rearchitect evaluatePure and side-effect tracking (#2587) 2018-10-12 15:45:50 -07:00
test Rearchitect evaluatePure and side-effect tracking (#2587) 2018-10-12 15:45:50 -07:00
website Website code and warnings (#2528) 2018-09-17 14:01:43 -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 Ignore project node_modules 2018-08-07 18:25:02 -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 New weekly branch: 0.2.55-alpha.0 2018-10-04 08:10:02 -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 Bump flow version (#2557) 2018-09-20 13:58:44 -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.