Summary:
We've had the node v6 test step failing for some time now (due to https://github.com/prettier/prettier/issues/3457).
Since there seems to be no progress on that issue, I'm adopting a similar approach that React Native has done to work around the issue: run the linter and flow on the latest nodejs version, and only run the jest tests on previous versions (this is also that `jest` seems to be doing as well).
For this I've created a `run-js-checks` step, while the jest tests are still under the `test-node-X` steps
Reviewed By: jeanlauliac
Differential Revision: D6770795
fbshipit-source-id: ba79caaf82c4b2fda5786a4cd3a9b2015c8b4537
Summary:
<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. The two fields below are mandatory. -->
**Summary**
As rafeca mentioned on Discord channel, `deploy` script fails. This PR is composed with intention to fix this error.
**Test plan**
- Try to deploy a new version using CircleCI config from this PR
<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. -->
Closes https://github.com/facebook/metro-bundler/pull/94
Reviewed By: mjesun
Differential Revision: D6405189
Pulled By: rafeca
fbshipit-source-id: 9adca768044515784474aa6f71ca6f733db5b07e
Summary:
<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. The two fields below are mandatory. -->
**Summary**
As we discussed on Discord channel on Nov 6th, this PR adds appropriate hooks to CircleCI in order to deploy successful builds (on master branch) to `npm` using tag that has been assigned to the latest commit.
This is how deployment process should look like:
Once you want to deploy, push a new tag to master. That will trigger a deployment script on CI. [According to CircleCI documentation](https://circleci.com/docs/1.0/npm-continuous-deployment/), the best way is to use
```
npm version x.y.z
```
in order to update package version and create git tag. Then, you can push your code using
```
git push --follow-tags
```
After successful build, a new version will be released.
<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
**Test plan**
Not sure if there is a way to properly test it before the merge. I think the only way is to merge it in, setup NPM_TOKEN env variable and try to create a new version by running build on CI. Please, let me know if you see alternative scenarios.
<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. -->
Closes https://github.com/facebook/metro-bundler/pull/88
Reviewed By: BYK, cpojer
Differential Revision: D6332813
Pulled By: rafeca
fbshipit-source-id: 1902afa8eb77a59e813cefc8e7f650a0106edfef
Rafael Oleza
Christoph Nakazawa
cpojer
Alexey
Alexey Kureev
Jean Lauliac