patrick/KaTeX
1
0
Fork 0
mirror of https://github.com/Smaug123/KaTeX synced 2025-10-05 03:08:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Replace yarn run and yarn install with yarn, remove building with npm instructions (#1528)

Browse Source 
* Replace `yarn run` with `yarn`

* Replace `yarn install` with `yarn`

* Remove building using `npm` from node.md
This commit is contained in:
ylemkimon
2018-07-30 14:31:25 +09:00
committed by GitHub
parent c88fa70a62
commit c06b36cb6a
10 changed files with 31 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
CONTRIBUTING.md
View File

@@ -58,7 +58,7 @@ single file. The goal is to have all functions use this new system.
## Testing
Local testing can be done by running the webpack-dev-server using configuration
`webpack.dev.js`. Run `yarn install` to install dependencies, and then `yarn start`
`webpack.dev.js`. Run `yarn` to install dependencies, and then `yarn start`
to start the server.
This will host an interactive editor at
@@ -74,7 +74,7 @@ by running `yarn add webpack-dev-server@2.7.1`.
The JavaScript parser and some of the HTML and MathML tree
builders are tested with Jest. These tests can be run using node with
`yarn run test:jest`. If you need to debug the tests see
`yarn test:jest`. If you need to debug the tests see
[https://facebook.github.io/jest/docs/troubleshooting.html](https://facebook.github.io/jest/docs/troubleshooting.html)
The interactive editor can also be used for debugging tests in the browser by
@@ -88,9 +88,9 @@ tests when you submit a pull request, in case you forget.
If you make any changes to Parser.js, add Jest tests to ensure they work.
Some tests verify the structure of the output tree using [snapshot testing](https://facebook.github.io/jest/docs/en/snapshot-testing.html).
Those snapshots can be updated by running `yarn run test:jest:update`.
Those snapshots can be updated by running `yarn test:jest:update`.
Also, test code coverage can be collected by `yarn run test:jest:coverage`.
Also, test code coverage can be collected by `yarn test:jest:coverage`.
You can view the report in `coverage/lcov-report/index.html`.
#### Screenshot tests
@@ -126,7 +126,7 @@ try to test in IE 9, using [modern.ie](http://modern.ie) VMs.
## Building
KaTeX is built using webpack with configuration `webpack.config.js`. Run
`yarn run build` to build the project.
`yarn build` to build the project.
## Style guide
@@ -141,12 +141,12 @@ Code
In general, try to make your code blend in with the surrounding code.
The code can be linted by running `yarn run test:lint`, which lints JavaScript
The code can be linted by running `yarn test:lint`, which lints JavaScript
files using ESLint and stylesheets using stylelint. They must pass to commit
the changes.
Some files have flowtype annotations and can be checked for type errors using
Flow by running `yarn run test:flow`. See [Flow](https://flow.org/) for more details.
Flow by running `yarn test:flow`. See [Flow](https://flow.org/) for more details.
## Pull Requests
@@ -160,7 +160,7 @@ Flow by running `yarn run test:flow`. See [Flow](https://flow.org/) for more det
The fonts for KaTeX live in a submodule stored in `submodules/katex-fonts`.
When you first clone the KaTeX repository, use
`git submodule update --init --recursive` to download the corresponding
fonts repository. After running `yarn install`, you should have Git hooks that
fonts repository. After running `yarn`, you should have Git hooks that
will automatically run this command after switching to branches
where `submodules/katex-fonts` point to different commits.