You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40 lines
2.3 KiB
Markdown
40 lines
2.3 KiB
Markdown
5 years ago
|
---
|
||
|
|
title: Development
|
||
|
|
editLink: false
|
||
|
|
---
|
||
|
6 years ago
|
|
||
|
|
PEG.js is currently maintained by [Futago-za Ryuu](https://github.com/futagoza) ([@futagozaryuu](https://twitter.com/futagozaryuu)).
|
||
|
|
|
||
|
|
Since it's [inception](https://www.google.com/search?q=inception+meaning) in 2010, PEG.js was maintained by [David Majda](https://majda.cz/) ([@dmajda](http://twitter.com/dmajda)), until [May 2017](https://github.com/pegjs/pegjs/issues/503).
|
||
|
|
|
||
|
5 years ago
|
::: warning
|
||
|
|
The [Bower package](https://github.com/pegjs/bower) (which was maintained by [Michel Krämer](http://www.michel-kraemer.com/) ([@michelkraemer](https://twitter.com/michelkraemer))) has been deprecated, and will no longer be updated.
|
||
|
|
:::
|
||
|
6 years ago
|
|
||
|
5 years ago
|
## Contribute
|
||
|
6 years ago
|
|
||
|
|
You are welcome to contribute code using [GitHub pull requests](https://github.com/pegjs/pegjs/pulls). Unless your contribution is really trivial you should get in touch with me first (preferably by creating a new issue on the [issue tracker](https://github.com/pegjs/pegjs/issues)) - this can prevent wasted effort on both sides.
|
||
|
|
|
||
|
|
> Before submitting a pull request, please make sure you've checked out the [Contribution Guidelines](https://github.com/pegjs/pegjs/blob/master/.github/CONTRIBUTING.md).
|
||
|
|
|
||
|
6 years ago
|
_Ensure you have Node.js v6+ and Yarn installed._
|
||
|
|
|
||
|
5 years ago
|
1. Create a fork of [https://github.com/pegjs/pegjs](https://github.com/pegjs/pegjs)
|
||
|
6 years ago
|
2. Clone your fork, and optionally create a new branch
|
||
|
6 years ago
|
3. Run the command `yarn install` from the root of your clone
|
||
|
6 years ago
|
4. Add and commit your changes
|
||
|
|
5. Validate your changes:
|
||
|
6 years ago
|
- Lint the JavaScript changes (command line only, run `yarn lint`)
|
||
|
|
- Run tests to ensure nothing's broken: `yarn test` from the root of the repository
|
||
|
|
- Run benchmarks to check performance: `yarn benchmark`
|
||
|
|
- Check the impact of your commits: [see separate documentation](https://github.com/pegjs/pegjs/blob/master/tools/impact/README.md)
|
||
|
6 years ago
|
6. If validation fails: reverse your commit, fix the problem and then add/commit again
|
||
|
|
7. Push the commits from your clone to the fork
|
||
|
|
8. From your fork, start a new pull request
|
||
|
|
|
||
|
6 years ago
|
It's also a good idea to check out the [package.json](https://github.com/pegjs/pegjs/blob/master/package.json) that defines various scripts.
|
||
|
6 years ago
|
|
||
|
|
To see the list of contributors check out the [repository's contributors page](https://github.com/pegjs/pegjs/graphs/contributors).
|
||
|
5 years ago
|
|
||
|
|
<PageFooter />
|