prettier/.travis.yml

---
language: node_js
node_js:
  - 4
  - stable
cache:
  yarn: true
  directories:
  - node_modules
env:
  - NODE_ENV=development
  - NODE_ENV=production
matrix:
  allow_failures:
    - env: NODE_ENV=production
  fast_finish: true
install:
  - yarn install --production=false
before_script:
  - if [ "${NODE_ENV}" = "production" ]; then yarn build; fi
script:
  - yarn lint
  - AST_COMPARE=1 yarn test -- --runInBand
  - if [ "${NODE_ENV}" = "development" ]; then yarn codecov; fi
deploy:
  provider: script
  script: website/deploy.sh
  skip_cleanup: true
  on:
    branch: master
    node: stable
add travis config and add yarn support 2017-01-11 18:52:51 +03:00			`---`
			`language: node_js`
			`node_js:`
			`- 4`
test on current release of node.js (#595) 2017-02-07 20:46:39 +03:00			`- stable`
add travis config and add yarn support 2017-01-11 18:52:51 +03:00			`cache:`
Enable yarn caching in .travis.yml (#1016) 2017-03-16 06:23:03 +03:00			`yarn: true`
add travis config and add yarn support 2017-01-11 18:52:51 +03:00			`directories:`
			`- node_modules`
Build/test dist/ on Travis (#2176) This helps us keep track of whether or not the dist/ build actually works (see https://github.com/prettier/prettier/pull/2174). Note that the dist/ jobs are allowed to fail, and do not affect overall build time, so they shouldn't slow anything down (see https://blog.travis-ci.com/2013-11-27-fast-finishing-builds/). 2017-06-18 02:37:51 +03:00			`env:`
			`- NODE_ENV=development`
			`- NODE_ENV=production`
			`matrix:`
			`allow_failures:`
			`- env: NODE_ENV=production`
			`fast_finish: true`
			`install:`
			`- yarn install --production=false`
			`before_script:`
			`- if [ "${NODE_ENV}" = "production" ]; then yarn build; fi`
Add `lint` script, run it on Travis, prettify source code (#1634) * Add `lint` script with eslint-plugin-prettier, use it in `format:all` See https://github.com/prettier/prettier/pull/1634#issuecomment-302945967 * Run `lint` script on Travis * Run Prettier on its own source code This was done with npm run format:all 2017-05-21 21:00:16 +03:00			`script:`
Improve ESLint setup and fix errors (#1656) * Improve ESLint setup - Uses `eslint:recommended` + a handful more rules. - Uses .eslintignore so that editors can understand which files to lint. - Uses .eslintrc<strong>.js</strong> so more editors get syntax highlighting. * Fix ESLint errors About half of them were fixed by `eslint . --fix`. 2017-05-21 22:11:09 +03:00			`- yarn lint`
Upgrade typescript parser, fix and run AST tests on Travis (#1657) * Run `yarn` to update yarn.lock * Upgrade typescript-eslint-parser, use JSXText instead of Literal for strings inside JSXElement https://github.com/eslint/typescript-eslint-parser/pull/272 was merged, so this fixes https://github.com/prettier/prettier/issues/1558 See here for more info about the new TSQualifiedName node type: https://github.com/eslint/typescript-eslint-parser/commit/3491b4b73a889b9f8cd32107f55ab62430ab9cdd * Run AST comparison tests on Travis 2017-05-22 00:16:24 +03:00			`- AST_COMPARE=1 yarn test -- --runInBand`
Enable code coverage in CI (#2497) * Enable code coverage in CI * Disable codecov comment * Ignore some statements from coverage reports 2017-07-16 14:49:37 +03:00			`- if [ "${NODE_ENV}" = "development" ]; then yarn codecov; fi`
Re-enable automatic deployment 2017-07-04 02:22:42 +03:00			`deploy:`
			`provider: script`
			`script: website/deploy.sh`
Enable code coverage in CI (#2497) * Enable code coverage in CI * Disable codecov comment * Ignore some statements from coverage reports 2017-07-16 14:49:37 +03:00			`skip_cleanup: true`
Re-enable automatic deployment 2017-07-04 02:22:42 +03:00			`on:`
			`branch: master`
			`node: stable`