OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2025-12-06 12:20:20 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
poc-event-registration
react/scripts/release
History
Dan Abramov 1ebeb0542f
Move npm output from build/packages/* to build/node_modules/* (#11962) 
* Move build/packages/* to build/node_modules/*

This fixes Node resolution in that folder and lets us require() packages in it in Node shell for manual testing.

* Link fixtures to packages/node_modules

This updates the location and also uses link: instead of file: to avoid Yarn caching the folder contents.
2018-01-04 19:01:31 +00:00
..
build-commands Add bundle linting and tests to the release script (#11662) 2017-11-26 16:47:20 +00:00
publish-commands Move npm output from build/packages/* to build/node_modules/* (#11962) 2018-01-04 19:01:31 +00:00
build.js Add bundle linting and tests to the release script (#11662) 2017-11-26 16:47:20 +00:00
config.js Release script tweaks (#11504) 2017-11-09 16:29:51 +00:00
package.json Release script (#11223) 2017-10-16 15:01:14 -07:00
publish.js Release script tweaks (#11504) 2017-11-09 16:29:51 +00:00
README.md Tweaked wording of release script README 2017-10-16 15:02:41 -07:00
utils.js Add bundle linting and tests to the release script (#11662) 2017-11-26 16:47:20 +00:00
yarn.lock Release script (#11223) 2017-10-16 15:01:14 -07:00

README.md

React Release Script

At a high-level, the release script runs in 2 passes: build and publish.

  1. The build script does the heavy lifting (eg checking CI, running automated tests, building Rollup bundles) and then prints instructions for manual verification.
  2. The publish script then publishes the built artifacts to NPM and pushes to GitHub.

Run either script without parameters to see its usage, eg:

./scripts/release/build.js
./scripts/release/publish.js

Each script will guide the release engineer through any necessary steps (including environment setup and manual testing steps).