facebookarchive/prepack
1
1
Fork 0
mirror of https://github.com/facebookarchive/prepack.git synced 2024-09-17 18:17:29 +03:00
Code Issues Projects Releases Wiki Activity
f3814460e2
prepack/package.json

123 lines
5.9 KiB
JSON
Raw Normal View History

Initial commit
2015-10-15 02:59:41 +03:00
{
"name": "prepack",
Weekly alpha 0.2.23-alpha.0 Summary: Marker for next alpha release Reviewed By: simonhj Differential Revision: D6838930 fbshipit-source-id: 2316b7edbb9ae8d2991ebf540528cb98d53697b2
2018-01-30 04:21:39 +03:00
"version": "0.2.23-alpha.0",
Mechanical search+replace renaming of everything relating to serializer.
2017-04-10 23:35:48 +03:00
"description": "Execute a JS bundle, serialize global state and side effects to a snapshot that can be quickly restored.",
We are no longer experimental.
2017-04-06 04:02:05 +03:00
"homepage": "https://github.com/facebook/prepack",
Moving things around so prepack 'run' can be included as a module
2017-03-30 01:48:22 +03:00
"repository": {
"type": "git",
We are no longer experimental.
2017-04-06 04:02:05 +03:00
"url": "git://github.com/facebook/prepack.git"
Moving things around so prepack 'run' can be included as a module
2017-03-30 01:48:22 +03:00
},
Initial commit
2015-10-15 02:59:41 +03:00
"bugs": {
We are no longer experimental.
2017-04-06 04:02:05 +03:00
"url": "https://github.com/facebook/prepack/issues"
Initial commit
2015-10-15 02:59:41 +03:00
},
"files": [
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"LICENSE",
"PATENTS",
"bin/",
"lib/"
Initial commit
2015-10-15 02:59:41 +03:00
],
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"bin": {
"prepack": "bin/prepack.js",
"prepack-repl": "bin/prepack-repl.js"
},
Refactor the public API in a similar style to Babel API (#469) * Refactor the public API This refactors the public Node API to mimic the [Babel API](http://babeljs.io/docs/usage/api/). This is a bit more idiomatic than "run CLI" or instantiate the full serializer object. I'm passing a single options object instead of individual arguments. This is a bit more managable as the option list grows. The prepack-node file is what is exposed in Node which has a file system API. Both synchronous and asynchronous forms. prepack-standalone is a module for environments without access to the file system such as browsers. I configure this to be exposed by default for such environments. That way we can also use this in the webpack build so that our own repl on the website can just use this public API. * Throw an error when serialization fails This lets any compiler flow to terminate properly by default but the error can safely be ignored if we've already printed error messages for it such as in the CLI. Turn internalDebug error messages off by default but allow it to be configured. * Added missing realm options Not yet exposed in the cli but available through the API.
2017-04-27 10:30:00 +03:00
"main": "lib/prepack-node.js",
"browser": "lib/prepack-standalone.js",
Initial commit
2015-10-15 02:59:41 +03:00
"scripts": {
Giving choice - npm or yarn. Summary: Fixing issue raised in #782. Closes https://github.com/facebook/prepack/pull/786 Differential Revision: D5394680 Pulled By: NTillmann fbshipit-source-id: b1f9f42425e759b68fbce5aa77f6d5a02e162756
2017-07-11 03:30:45 +03:00
"build": "babel src --out-dir lib --source-maps && yarn build-bundle",
Enable source map for scripts Summary: Enables source map for scripts folder so that we can debug test runners. Closes https://github.com/facebook/prepack/pull/819 Differential Revision: D5444607 Pulled By: yinghuitan fbshipit-source-id: ac80516dfb9f91e469cfc2d4a0c8c3108f78d83e
2017-07-18 21:42:05 +03:00
"build-scripts": "babel scripts --out-dir lib --source-maps",
Create a webpack bundle entry point (#364)
2017-04-07 04:52:15 +03:00
"build-bundle": "webpack",
New serializer tester is es6 so the the build rules in the package.json file have been updated to accomodate this change
2017-06-12 22:17:21 +03:00
"watch": "babel src scripts --out-dir lib --watch --source-maps",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"lint": "eslint src scripts",
Do not introduce new block scopes for eval scripts (#432) * Do not introduce new block scopes for eval scripts * Update function.js
2017-04-20 20:35:38 +03:00
"flow": "flow check",
New serializer tester is es6 so the the build rules in the package.json file have been updated to accomodate this change
2017-06-12 22:17:21 +03:00
"test-residual": "babel-node scripts/test-residual.js",
More error messages for binary ops Summary: Add message for < > >= <= != == Also run more tests with code coverage. Closes https://github.com/facebook/prepack/pull/728 Differential Revision: D5280091 Pulled By: hermanventer fbshipit-source-id: b6e96451940cecde4bd8e494b4fe55a93c78e984
2017-06-20 02:59:25 +03:00
"test-residual-with-coverage": "./node_modules/.bin/istanbul cover ./lib/test-residual.js --dir coverage.residual && ./node_modules/.bin/remap-istanbul -i coverage.residual/coverage.json -o coverage-sourcemapped.residual -t html",
Catch fatal errors in visitName. Summary: Introspection errors no longer show up as completions, so any time we evaluate a node that might cause an introspection error, we should expect to catch and handle a FatalError. Also tweaked package.json to allow longer stack traces when running test-serializer and tweaked test-internal to output error messages that do not have associated source locations. (The latter should not happen in practice but could happen when things go wrong.) Closes https://github.com/facebook/prepack/pull/866 Differential Revision: D5563965 Pulled By: hermanventer fbshipit-source-id: e2a74ec19314703526ebd35f7b8e694c19d82ab0
2017-08-04 21:05:40 +03:00
"test-serializer": "babel-node --stack_trace_limit=200 --stack_size=10000 scripts/test-runner.js",
More error messages for binary ops Summary: Add message for < > >= <= != == Also run more tests with code coverage. Closes https://github.com/facebook/prepack/pull/728 Differential Revision: D5280091 Pulled By: hermanventer fbshipit-source-id: b6e96451940cecde4bd8e494b4fe55a93c78e984
2017-06-20 02:59:25 +03:00
"test-serializer-with-coverage": "./node_modules/.bin/istanbul cover ./lib/test-error-handler.js --dir coverage.error && ./node_modules/.bin/istanbul cover ./lib/test-runner.js && ./node_modules/.bin/remap-istanbul -i coverage.error/coverage.json -i coverage/coverage.json -o coverage-sourcemapped -t html",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"test-sourcemaps": "babel-node scripts/generate-sourcemaps-test.js && bash < scripts/test-sourcemaps.sh",
"test-test262": "babel-node scripts/test262-runner.js",
Add yet another test to time out list. (#665)
2017-05-22 21:52:41 +03:00
"test-test262-nightly": "NIGHTLY_BUILD=true babel-node -- scripts/test262-runner.js",
Use integration api to run Test262 tests Summary: This method provides an alternative way to run Test262 through a stream of compiled test contents for each scenario (default, strict mode), including all the necessary harness contents. The logic to capture an execution success or failure is similar to the original one - from scripts/test262-runner.js - and improvements should be done as follow ups. The filtering system is now done through a configuration yaml file, using tests metadata and path locations. This filter is used as an object that can be extended with further logic, but still offers a single point to check for filtering. The report system requires some improvements and these should also be done as follow-ups. For now they provide a report for each folder and the total results. Although, the results data contain enough information to highly expand the report. Some further improvements are expected and planned, this work should be at least ready for an initial round for feedback review. Closes https://github.com/facebook/prepack/pull/1122 Reviewed By: cblappert Differential Revision: D6456700 Pulled By: hermanventer fbshipit-source-id: ba56efcaa4eab847594cb7c1fbc908cf1fc66a80
2017-12-02 04:37:47 +03:00
"test-test262-new": "babel-node scripts/test262.js",
Serialize independent functions Summary: Currently works for all test cases except `noconflict-existantobject.js`. There are a couple things that are dubious in the current implementation that I will address as I iterate on it: * We don't visit things correctly in the visitor or the serializer -- we should be visiting only: * generator entries in effects * Bindings, PropertyBindings in effects not relating to CreatedObjects * There is currently no way to emit to the main body after the main generator has been serialized -- we may need to if a value is only reachable from one of the additional functions. * More thought needs to go into how this interacts with * speculative initialization * require optimization * inlining Closes https://github.com/facebook/prepack/pull/912 Differential Revision: D5859741 Pulled By: cblappert fbshipit-source-id: 9fe7bd4429ad53629582f9fb7154a28971159554
2017-09-26 02:50:15 +03:00
"test-internal": "babel-node --stack_size=10000 --stack_trace_limit=200 --max_old_space_size=16384 scripts/test-internal.js",
More error messages for binary ops Summary: Add message for < > >= <= != == Also run more tests with code coverage. Closes https://github.com/facebook/prepack/pull/728 Differential Revision: D5280091 Pulled By: hermanventer fbshipit-source-id: b6e96451940cecde4bd8e494b4fe55a93c78e984
2017-06-20 02:59:25 +03:00
"test-error-handler": "babel-node scripts/test-error-handler.js",
"test-error-handler-with-coverage": "./node_modules/.bin/istanbul cover ./lib/test-error-handler.js --dir coverage.error && ./node_modules/.bin/remap-istanbul -i coverage.error/coverage.json -o coverage-sourcemapped.error -t html",
Add minimal test case for the node-cli mode I enable this mode only on CI for now. Not to `yarn test`. Since it is locked to a particular version of Node so we don't want to force people to run it locally.
2017-05-13 05:20:24 +03:00
"test-node-cli-mode": "bash < scripts/test-node-cli-mode.sh",
Change processSerializedCode func to receive error as 1st arg Summary: Since example code of [How to run Prepack](https://github.com/facebook/prepack#how-to-run-prepack) doesn't work(https://github.com/facebook/prepack/issues/781 ) I fixed `processSerializedCode` function to handle error as 1st argument which follows 'error first callback' convention. And to verify the changes I've added test code for the case of `StdIn` Closes https://github.com/facebook/prepack/pull/784 Differential Revision: D5375275 Pulled By: NTillmann fbshipit-source-id: ea85d0f30db4305aa7fcb5b69bf28f5998a84962
2017-07-06 22:35:04 +03:00
"test-std-in": "bash < scripts/test-std-in.sh",
Add React/Jest testing infrastructure Summary: Release note: none This PR adds the React/Jest testing infrastructure to Prepack and is stacked on the PR https://github.com/facebook/prepack/pull/1117. Thus, that PR should be merged before this PR is merged to reduce noise in the diff. This will allow us to test various runtime outputs of React 16 when running original source vs Prepacked source to see if there are any issues/differences that might have an impact on applications. The primary reason for this is to track regressions for the component folding PRs that will land in the future. Please note, this PR does not contain any reconciler changes, thus `__registerReactComponentRoot(App);` has been commented out of tests to ensure they don't prematurely fail. A follow up PR will enable them once the other React functional component folding PRs get landed. This PR also adds some mock React globals to be used within tests (and maybe to be further integrated into folding at a future point too). The mocks include `React.Component` and `React.cloneElement` for now. Furthermore, a `utils/json.js` utility file exists to help normalize the results from the React test renderer so that adjacent JSON text nodes get merged, which is something that may exist because of how the reconciler (once the PR lands) handles inlining of child nodes. The command to run React tests is `yarn test-react`. Closes https://github.com/facebook/prepack/pull/1118 Reviewed By: cblappert Differential Revision: D6208263 Pulled By: trueadm fbshipit-source-id: d54f3b0e1cc3240e1f142d3da08bc279e4153889
2017-11-02 14:28:37 +03:00
"test-react": "jest scripts/test-react",
Handle computed property names using loop variables Summary: Initial bit of support for dealing with abstract loops where the loop body contains assignments to properties with computed names involving loop controlled variables. Closes https://github.com/facebook/prepack/pull/1286 Differential Revision: D6628885 Pulled By: hermanventer fbshipit-source-id: 960fa469e3c18e55e5447ac441235a80df2b1629
2017-12-23 00:12:35 +03:00
"test": "yarn test-residual && yarn test-serializer && yarn test-sourcemaps && yarn test-error-handler && yarn test-std-in && yarn test-test262 && yarn test-internal && yarn test-react",
New code coverage step Summary: Adds new `test-coverage-all` command to `package.json` which will run and compose all test coverage information into one html. Reviewed By: hermanventer Differential Revision: D6052366 fbshipit-source-id: 208259fa79185267f6c7a51ca8baf08ffb707e97
2017-10-20 03:48:24 +03:00
"test-coverage-most": "./node_modules/.bin/istanbul --stack_size=10000 --max_old_space_size=16384 cover ./lib/multi-runner.js --dir coverage.most && ./node_modules/.bin/remap-istanbul -i coverage.most/coverage.json -o coverage-sourcemapped -t html",
"test-all-coverage": "./node_modules/.bin/istanbul --stack_size=10000 --max_old_space_size=16384 cover ./lib/multi-runner.js --dir coverage.most && ./node_modules/.bin/istanbul --stack_size=10000 --max_old_space_size=16384 cover -- ./lib/test262-runner.js --timeout 50 --singleThreaded && ./node_modules/.bin/remap-istanbul -i coverage/coverage.json -i coverage.most/coverage.json -o coverage-sourcemapped -t html",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"repl": "node lib/repl-cli.js",
Analyze residual functions Summary: Release note: Provide a way to analyze residual functions for Prepack errors Since the analysis takes a while, the --check option now takes start and count parameters so that a subrange of functions can be analyzed. Each function is analyzed only in the context of the heap as it was at the end of global code execution and the arguments supplied to the analysis are all simple partial abstract objects, so that the analysis of a function does not come to screeching halt every time a parameter is used as the object of a member expression or as the argument of an operator. A number of tweaks to the handling of simple objects will be in a follow up pull request. Closes https://github.com/facebook/prepack/pull/1379 Differential Revision: D6876045 Pulled By: hermanventer fbshipit-source-id: 4d192cc6cf222b3986114362c5642a949f292845
2018-02-02 01:13:20 +03:00
"precheck": "yarn prepack --check",
"prepack": "node --stack_size=10000 --stack_trace_limit=200 --max_old_space_size=16384 lib/prepack-cli.js --accelerateUnsupportedRequires --compatibility jsc-600-1-4-17 --delayUnsupportedRequires --mathRandomSeed 0 ",
Leave a residual function in prepack-cli (#655) This lets us prepack Prepack itself using the node-cli option. Added a yarn shortcut to run it with the required flags. Just for fun.
2017-05-23 17:24:00 +03:00
"prepack-prepack": "node --stack_size=10000 --max_old_space_size=8096 ./bin/prepack.js ./lib/prepack-cli.js --out ./lib/prepack-cli.prepacked.js --compatibility node-cli --mathRandomSeed rnd",
Downgrade errors to warnings when speculatively prepacking modules Summary: There were two instances of the pattern and the second contained an omission that broke it. Factored out the pattern and made sure it works in both cases now. Closes https://github.com/facebook/prepack/pull/851 Differential Revision: D5523645 Pulled By: hermanventer fbshipit-source-id: 086cf9aadb1e31279ae11b512f367daddf726d55
2017-07-29 05:31:58 +03:00
"validate": "yarn build && yarn build-scripts && yarn lint && yarn depcheck && yarn flow && yarn test",
Giving choice - npm or yarn. Summary: Fixing issue raised in #782. Closes https://github.com/facebook/prepack/pull/786 Differential Revision: D5394680 Pulled By: NTillmann fbshipit-source-id: b1f9f42425e759b68fbce5aa77f6d5a02e162756
2017-07-11 03:30:45 +03:00
"prepublish": "yarn build",
Enable Prettier and remove conflicting eslint rules. Summary: Per discussion in #729, this sets up prettier but doesn't actually run it on the codebase. Closes https://github.com/facebook/prepack/pull/759 Reviewed By: Kishore-B-Rao Differential Revision: D5343135 Pulled By: NTillmann fbshipit-source-id: 638740d48b6fa797fa79b8b5fd3c032497cb0132
2017-06-29 22:16:33 +03:00
"depcheck": "babel-node scripts/detect_bad_deps.js",
Making Prettier a check-in gate Summary: This supersedes #760. Additional changes over #760: Pinning Prettier version to get some formatting always. (Different prettier versions were responsible for the observed flip-flopping of StringPrototype.js.) Print output of prettier in wrapper script for better diagnosis / experience. (TODO: How to just pipe through console output? Couldn't get it to work.) Updating problematic .js file for the last time. Closes https://github.com/facebook/prepack/pull/787 Differential Revision: D5382336 Pulled By: NTillmann fbshipit-source-id: 95ed988ef3f091493d2fb509b5481753d56901cd
2017-07-07 21:28:43 +03:00
"prettier": "node ./scripts/prettier.js write-changed",
Downgrade errors to warnings when speculatively prepacking modules Summary: There were two instances of the pattern and the second contained an omission that broke it. Factored out the pattern and made sure it works in both cases now. Closes https://github.com/facebook/prepack/pull/851 Differential Revision: D5523645 Pulled By: hermanventer fbshipit-source-id: 086cf9aadb1e31279ae11b512f367daddf726d55
2017-07-29 05:31:58 +03:00
"prettier-all": "node ./scripts/prettier.js write"
Initial commit
2015-10-15 02:59:41 +03:00
},
"dependencies": {
Basic JSX/ReactElement support Summary: Release notes: adds JSX and ReactElement evaluation/serialization support This adds JSX/ReactElement support to the Prepack serializer so `ReactElement` "like" objects can correctly be converted back to JSX syntax. Example: ```jsx 'use strict'; const externalThing = __abstract('function', 'externalThing'); function Test() { return <div>{ externalThing() }</div> } global.test = Test; ``` Becomes: ```jsx 'use strict'; var _$0 = this; var _0 = function () { return <div>{_1()}</div>; }; var _1 = externalThing; _$0.test = _0; ``` I've also added a JSXElement -> ReactElement evaluator. Closes https://github.com/facebook/prepack/pull/1051 Differential Revision: D6053275 Pulled By: trueadm fbshipit-source-id: 7c31545751ceedba55cdd4581bc6de51a98b412a
2017-10-13 22:01:26 +03:00
"babel-core": "^6.26.0",
Initial commit
2015-10-15 02:59:41 +03:00
"babel-generator": "^6.8.0",
Basic JSX/ReactElement support Summary: Release notes: adds JSX and ReactElement evaluation/serialization support This adds JSX/ReactElement support to the Prepack serializer so `ReactElement` "like" objects can correctly be converted back to JSX syntax. Example: ```jsx 'use strict'; const externalThing = __abstract('function', 'externalThing'); function Test() { return <div>{ externalThing() }</div> } global.test = Test; ``` Becomes: ```jsx 'use strict'; var _$0 = this; var _0 = function () { return <div>{_1()}</div>; }; var _1 = externalThing; _$0.test = _0; ``` I've also added a JSXElement -> ReactElement evaluator. Closes https://github.com/facebook/prepack/pull/1051 Differential Revision: D6053275 Pulled By: trueadm fbshipit-source-id: 7c31545751ceedba55cdd4581bc6de51a98b412a
2017-10-13 22:01:26 +03:00
"babel-plugin-transform-react-jsx": "^6.24.1",
Initial commit
2015-10-15 02:59:41 +03:00
"babel-template": "^6.9.0",
"babel-traverse": "^6.9.0",
"babel-types": "^6.9.0",
Upgrade to babylon@6.18.0 Summary: babylon@6.18.0 has support for "opaque type alias" syntax (https://github.com/babel/babylon/releases/tag/v6.18.0 and https://medium.com/flow-type/hiding-implementation-details-with-flows-new-opaque-type-aliases-feature-40e188c2a3f9). Reviewed By: cblappert Differential Revision: D5706930 fbshipit-source-id: 8cdaee77b838812ebb012a352f7e77b74838b536
2017-08-30 02:14:39 +03:00
"babylon": "^6.18.0",
Initial commit
2015-10-15 02:59:41 +03:00
"base62": "^1.1.2",
Framework for debug adapter and mock ui Summary: Release note: none Issue: #907 - Mock UI as a CLI to communicate with the adapter - Starter code for the debugger adapter with an initialize request Closes https://github.com/facebook/prepack/pull/1088 Differential Revision: D6108024 Pulled By: JWZ2018 fbshipit-source-id: 506ec039dcb1ff540872cb2e1a87a165cfd22e4d
2017-10-20 20:52:42 +03:00
"queue-fifo": "^0.2.3",
Initial commit
2015-10-15 02:59:41 +03:00
"seedrandom": "^2.4.2",
Framework for debug adapter and mock ui Summary: Release note: none Issue: #907 - Mock UI as a CLI to communicate with the adapter - Starter code for the debugger adapter with an initialize request Closes https://github.com/facebook/prepack/pull/1088 Differential Revision: D6108024 Pulled By: JWZ2018 fbshipit-source-id: 506ec039dcb1ff540872cb2e1a87a165cfd22e4d
2017-10-20 20:52:42 +03:00
"source-map": "^0.5.6",
"vscode-debugadapter": "^1.24.0",
"vscode-debugprotocol": "^1.24.0"
Initial commit
2015-10-15 02:59:41 +03:00
},
"devDependencies": {
"babel-cli": "^6.18.0",
"babel-eslint": "^7.1.1",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"babel-helper-function-name": "^6.8.0",
"babel-helper-get-function-arity": "^6.8.0",
Initial commit
2015-10-15 02:59:41 +03:00
"babel-plugin-transform-class-properties": "^6.6.0",
"babel-plugin-transform-object-rest-spread": "^6.8.0",
Use preset-env (#512)
2017-05-24 00:30:54 +03:00
"babel-preset-env": "^1.4.0",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"babel-preset-react": "^6.5.0",
"chalk": "^1.1.3",
Initial commit
2015-10-15 02:59:41 +03:00
"eslint": "^3.8.1",
"eslint-plugin-babel": "^3.3.0",
"eslint-plugin-flow-header": "^0.1.1",
"eslint-plugin-flowtype": "^2.20.0",
"eslint-plugin-header": "^1.0.0",
Enable eslint prettier plugin Summary: After adding this plugin, you just need to install https://github.com/AtomLinter/linter-eslint Atom package to surface ESLint errors(including prettier errors) in Nuclide linter UI. You also got auto-fix support in the Nuclide UI. Similarly, in VSCode, you can install https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint plugin to surface ESLint error in VSCode UI. One caveat is that, eslint-plugin-prettier uses its own version of prettier(1.3.1) which may diverge from what we want. If we really found a file that diverge in formatting, we may have to add it into .eslintignore to ignore from UI/linter. Closes https://github.com/facebook/prepack/pull/816 Differential Revision: D5444642 Pulled By: yinghuitan fbshipit-source-id: 1670129d62e5e799a50c53d78387b5ded4c2c964
2017-07-18 23:53:50 +03:00
"eslint-plugin-prettier": "^2.1.2",
Update flow version Summary: Update Flow to version 61 and deal with changes in the behavior of Flow. Reviewed By: yinghuitan Differential Revision: D6631584 fbshipit-source-id: f00c2707bcb991ffbdb3e2e74b6a49032f06a5e4
2017-12-23 04:14:13 +03:00
"flow-bin": "^0.61.0",
Initial commit
2015-10-15 02:59:41 +03:00
"graceful-fs": "^4.1.11",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"invariant": "^2.2.0",
"istanbul": "^0.4.5",
Add React/Jest testing infrastructure Summary: Release note: none This PR adds the React/Jest testing infrastructure to Prepack and is stacked on the PR https://github.com/facebook/prepack/pull/1117. Thus, that PR should be merged before this PR is merged to reduce noise in the diff. This will allow us to test various runtime outputs of React 16 when running original source vs Prepacked source to see if there are any issues/differences that might have an impact on applications. The primary reason for this is to track regressions for the component folding PRs that will land in the future. Please note, this PR does not contain any reconciler changes, thus `__registerReactComponentRoot(App);` has been commented out of tests to ensure they don't prematurely fail. A follow up PR will enable them once the other React functional component folding PRs get landed. This PR also adds some mock React globals to be used within tests (and maybe to be further integrated into folding at a future point too). The mocks include `React.Component` and `React.cloneElement` for now. Furthermore, a `utils/json.js` utility file exists to help normalize the results from the React test renderer so that adjacent JSON text nodes get merged, which is something that may exist because of how the reconciler (once the PR lands) handles inlining of child nodes. The command to run React tests is `yarn test-react`. Closes https://github.com/facebook/prepack/pull/1118 Reviewed By: cblappert Differential Revision: D6208263 Pulled By: trueadm fbshipit-source-id: d54f3b0e1cc3240e1f142d3da08bc279e4153889
2017-11-02 14:28:37 +03:00
"jest": "^21.2.1",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"js-yaml": "^3.6.1",
"jsdom": "^9.2.1",
Create a webpack bundle entry point (#364)
2017-04-07 04:52:15 +03:00
"kcheck": "^2.0.0",
Break ecma deps (#400) * Refactor realm constructor * Refactor types.js to not depend on methods/ * Fix errors, add verifier to prevent cycles * Fixed comments * Fixing tests * Fix merge bug
2017-04-15 01:09:34 +03:00
"madge": "^1.6.0",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"minimist": "^1.2.0",
Making Prettier a check-in gate Summary: This supersedes #760. Additional changes over #760: Pinning Prettier version to get some formatting always. (Different prettier versions were responsible for the observed flip-flopping of StringPrototype.js.) Print output of prettier in wrapper script for better diagnosis / experience. (TODO: How to just pipe through console output? Couldn't get it to work.) Updating problematic .js file for the last time. Closes https://github.com/facebook/prepack/pull/787 Differential Revision: D5382336 Pulled By: NTillmann fbshipit-source-id: 95ed988ef3f091493d2fb509b5481753d56901cd
2017-07-07 21:28:43 +03:00
"prettier": "1.5.2",
Add React/Jest testing infrastructure Summary: Release note: none This PR adds the React/Jest testing infrastructure to Prepack and is stacked on the PR https://github.com/facebook/prepack/pull/1117. Thus, that PR should be merged before this PR is merged to reduce noise in the diff. This will allow us to test various runtime outputs of React 16 when running original source vs Prepacked source to see if there are any issues/differences that might have an impact on applications. The primary reason for this is to track regressions for the component folding PRs that will land in the future. Please note, this PR does not contain any reconciler changes, thus `__registerReactComponentRoot(App);` has been commented out of tests to ensure they don't prematurely fail. A follow up PR will enable them once the other React functional component folding PRs get landed. This PR also adds some mock React globals to be used within tests (and maybe to be further integrated into folding at a future point too). The mocks include `React.Component` and `React.cloneElement` for now. Furthermore, a `utils/json.js` utility file exists to help normalize the results from the React test renderer so that adjacent JSON text nodes get merged, which is something that may exist because of how the reconciler (once the PR lands) handles inlining of child nodes. The command to run React tests is `yarn test-react`. Closes https://github.com/facebook/prepack/pull/1118 Reviewed By: cblappert Differential Revision: D6208263 Pulled By: trueadm fbshipit-source-id: d54f3b0e1cc3240e1f142d3da08bc279e4153889
2017-11-02 14:28:37 +03:00
"react": "^16.0.0",
"react-test-renderer": "^16.0.0",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"remap-istanbul": "^0.9.1",
"source-map-support": "^0.4.6",
Use integration api to run Test262 tests Summary: This method provides an alternative way to run Test262 through a stream of compiled test contents for each scenario (default, strict mode), including all the necessary harness contents. The logic to capture an execution success or failure is similar to the original one - from scripts/test262-runner.js - and improvements should be done as follow ups. The filtering system is now done through a configuration yaml file, using tests metadata and path locations. This filter is used as an object that can be extended with further logic, but still offers a single point to check for filtering. The report system requires some improvements and these should also be done as follow-ups. For now they provide a report for each folder and the total results. Although, the results data contain enough information to highly expand the report. Some further improvements are expected and planned, this work should be at least ready for an initial round for feedback review. Closes https://github.com/facebook/prepack/pull/1122 Reviewed By: cblappert Differential Revision: D6456700 Pulled By: hermanventer fbshipit-source-id: ba56efcaa4eab847594cb7c1fbc908cf1fc66a80
2017-12-02 04:37:47 +03:00
"test262-integrator": "^1.2.0",
Extract scripts from npm package (#463) This moves things around in a more common idiomatic folder structure / naming convention. This extracts the scripts that are only used to test the library from the source of the library itself. /src/scripts -> /scripts This is no longer part of the build process. Therefore we use babel-node to run the files as needed. The exception is test-runner that is just ran in plain node so that it works with the coverage reports. The lib folder now includes only and all the library files required to use the package and no longer test runners. Because of that I moved all the dependencies that were related only to our test scripts and website build to devDependencies. That way we minimize the required dependencies to use Prepack downstream as an npm package. Then I configured the package.json to only list lib/ and bin/ folders as part of the package. This lets `npm publish` ignore all other files so that people installing the package don't need to include all our testing code. I added files to bin/ and package.json which is a convention to make this package installable and usable as a command-line tool. Renamed run_util -> prepack-cli and repl -> repl-cli to separate these from library variants. The coverage reports now get created in the root instead of lib folder so that they don't get included in the build. I bumped the version number to one minor above what is already on npm since we can't publish earlier than that.
2017-04-26 22:26:18 +03:00
"uglify-js": "^2.6.2",
Create a webpack bundle entry point (#364)
2017-04-07 04:52:15 +03:00
"webpack": "^2.3.3"
Initial commit
2015-10-15 02:59:41 +03:00
},
"engines": {
Bump node version (#721)
2017-06-13 00:36:56 +03:00
"node": ">=6.1.0"
Initial commit
2015-10-15 02:59:41 +03:00
},
"keywords": [
"prepack"
],
"license": "BSD-3-Clause",
Add React/Jest testing infrastructure Summary: Release note: none This PR adds the React/Jest testing infrastructure to Prepack and is stacked on the PR https://github.com/facebook/prepack/pull/1117. Thus, that PR should be merged before this PR is merged to reduce noise in the diff. This will allow us to test various runtime outputs of React 16 when running original source vs Prepacked source to see if there are any issues/differences that might have an impact on applications. The primary reason for this is to track regressions for the component folding PRs that will land in the future. Please note, this PR does not contain any reconciler changes, thus `__registerReactComponentRoot(App);` has been commented out of tests to ensure they don't prematurely fail. A follow up PR will enable them once the other React functional component folding PRs get landed. This PR also adds some mock React globals to be used within tests (and maybe to be further integrated into folding at a future point too). The mocks include `React.Component` and `React.cloneElement` for now. Furthermore, a `utils/json.js` utility file exists to help normalize the results from the React test renderer so that adjacent JSON text nodes get merged, which is something that may exist because of how the reconciler (once the PR lands) handles inlining of child nodes. The command to run React tests is `yarn test-react`. Closes https://github.com/facebook/prepack/pull/1118 Reviewed By: cblappert Differential Revision: D6208263 Pulled By: trueadm fbshipit-source-id: d54f3b0e1cc3240e1f142d3da08bc279e4153889
2017-11-02 14:28:37 +03:00
"author": "Facebook",
"jest": {
"testMatch": [
"**/scripts/test-react.js"
]
}
Initial commit
2015-10-15 02:59:41 +03:00
}
Reference in New Issue Copy Permalink