You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+26-16Lines changed: 26 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,19 @@
1
-
Contributing
2
-
============
1
+
# Contributing
3
2
4
3
Thanks for contributing!
5
4
6
5
## Before you contribute
7
6
8
-
This package is a fork of [fast-deep-equal](https://github.com/epoberezkin/fast-deep-equal). This library has added handling for React. Before contributing, _please make sure the issue relates directly to this library and not fast-deep-equals_.
7
+
This package is a fork of [fast-deep-equal](https://github.com/epoberezkin/fast-deep-equal). This library has added handling for React.
8
+
Before contributing, _please make sure the issue relates directly to this library and not fast-deep-equal_.
9
9
10
10
We encourage pull requests concerning:
11
11
12
12
* React features not handled in this library
13
-
* Integrating updates from `fast-deep-equal`. This unfortunately, now requires more manual work to use the comment blocks in `index.js` to figure out what to paste and where.
14
-
* Integrating tests from `fast-deep-equal`. This usually entails upgrading the `git`-based dependencies of `fast-deep-equal-git` and `npm`-published package of `fast-deep-equal` in `package.json:devDependencies`.
13
+
* Integrating updates from `fast-deep-equal` - This, unfortunately, now requires more manual work. Use the comment blocks in `index.js`
14
+
to figure out what to paste and where.
15
+
* Integrating tests from `fast-deep-equal` - This usually entails upgrading the `git`-based dependencies of `fast-deep-equal-git` and
16
+
`npm`-published package of `fast-deep-equal` in `package.json:devDependencies`.
15
17
* Bugs in this library
16
18
* New tests for React
17
19
* Documentation
@@ -30,7 +32,7 @@ Install the project using `yarn` (which we've standardized on for development):
30
32
$ yarn install
31
33
```
32
34
33
-
`tl;dr` -- Everything you normally need to run is aggregated into:
35
+
**TL; DR:** - Everything you normally need to run is aggregated into:
34
36
35
37
```sh
36
38
$ yarn run test
@@ -106,24 +108,32 @@ $ yarn -s compress
106
108
$ yarn size-min-gz
107
109
```
108
110
109
-
**Note**: If the min+gz size increases, please note it in the README. If it is a significant increase, please flag to your reviewers and have a discussion about whether or not the size addition is justified.
111
+
**Note**: If the min+gz size increases, please note it in the README. If it is a significant increase,
112
+
please flag to your reviewers and have a discussion about whether or not the size addition is justified.
110
113
111
114
## Before submitting a PR...
112
115
113
-
Before you go ahead and submit a PR, make sure that you have done the following:
116
+
... please make sure that you have done the following:
114
117
115
-
```sh
116
-
$ yarn run test
117
-
$ yarn run benchmark
118
-
```
118
+
1. Confirm that all checks are passing:
119
+
120
+
```sh
121
+
$ yarn run test
122
+
$ yarn run benchmark
123
+
```
124
+
125
+
2. Confirm we don't have any significant performance regressions (check out `master` for a baseline comparison on _your_ machine).
119
126
120
-
1. Everything must be correct / pass checks.
121
-
2. You should also check the benchmark stats and make sure that we don't have any significant performance regressions (check out `master` for a baseline comparison on _your_ machine).
122
-
- Please **do** update the README benchmark numbers for changes in your PR so that we have much easier discussion points _and_ our users get up-to-date information.
127
+
3. Confirm you aren't impacting our bundle size.
128
+
If you _do_ affect the bundle size, please update the bundle badge in the Readme by
129
+
* Following the steps outlined in [size](#size):
130
+
`yarn -s compress && yarn size-min-gz`
131
+
* Grabbing that output and replacing the current size in the bundle_img: (`https://img.shields.io/badge/minzipped%20size-<NEW_SIZE>%20B-flatgreen.svg`)
132
+
For example, if the new size is `650`, the new bundle_img will be `https://img.shields.io/badge/minzipped%20size-650%20B-flatgreen.svg`
123
133
124
134
## Releasing a new version to NPM
125
135
126
-
_Only for project administrators_.
136
+
_Only for project administrators_
127
137
128
138
1. Run `npm version patch` (or `minor|major|VERSION`) to run tests and lint,
129
139
build published directories, then update `package.json` + add a git tag.
0 commit comments