vitalif
/
prettier
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
prettier/.travis.yml

25 lines
473 B
YAML
Raw Normal View History

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:
fast_finish: true
install:
Fix Travis production builds (#2933) * Fix Travis production builds * Fix Travis production builds, attempt 2 * Remove `allow_failures` in .travis.yml The reason we allowed the production builds to fail in the first place: ❯ git show 532ac0d3f commit 532ac0d3f8931f1c272ae55453bfa64a3f68db5f Author: Joseph Frazier <1212jtraceur@gmail.com> Date: 2017-06-17 19:37:51 -0400 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/). However, as we discovered in #2933 requiring the production builds to succeed only adds about 1 minute of build time, so it is not worth the risk of missing that the production builds fail.
2017-09-29 10:34:47 +03:00
- NODE_ENV=development yarn install
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
before_script:
Move all docs to website (#3139) * Sync README -> docs/options.md * Sync README -> docs/*.md * Misc fixups * Remove markdown-toc * Remove insert-pragma from ToC * Never again! * Move all docs to ./docs * Remove yarn toc * Fix inter-doc links * Fix links in footer * Clean up README.md * Add basic description to README.md * Use flat badges * Move editor guides to website * Improve prettier-ignore docs * Fixup bad find/replace * Add JSON to README * Fix custom parser API link * Fixup GitHub centering, add downloads badge * Add 1.8 docs * docs(website): mention markdown on homepage (#1) * Add intro * Add watching-files.md * Fix markdown syntax highlighting * Switch back to .md links
2017-11-07 06:39:07 +03:00
- yarn check-deps
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
- 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
chore: setup markdown formatting (#3224) * chore(deps): upgrade prettier to v1.8.2 * chore: setup lint-docs script * docs: add `<!-- prettier-ignore -->`s * docs: format docs * Revert "docs: format docs" This reverts commit 6dba903987dddc498cb589ca311905f25b6aee53. * chore(prettierrc): set `--no-prose-wrap` * docs: format docs * Revert "docs: format docs" This reverts commit 139bd744b6921916be8fac4fa3bab83bae5d12df. * docs: tweak * docs: format docs * chore: rename .prettierrc * chore: rename back to .prettierrc * chore: split out third-party * refactor: fix linting * chore: do not split out third-party on website
2017-11-22 14:27:40 +03:00
- yarn lint-docs
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