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
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,11 +28,16 @@ Start reading our code, and you'll get the hang of it. We optimize for readabili
28
28
Local development configuration is pretty snappy. Here's how to get set up:
29
29
30
30
1. Install/use node >=16.0.0
31
+
1. Install/use yarn <=1.x.x
31
32
1. Run `yarn link` from project root
32
33
1. Run `cd docs-site && yarn link react-datepicker`
33
34
1. Run `yarn install` from project root
34
35
1. Run `yarn build` from project root (at least the first time, this will get you the `dist` directory that holds the code that will be linked to)
35
-
1. Run `yarn start` from project root
36
+
1. Run `yarn start` from project root. (This command launches a documentation app and runs it as a simple webserver at http://localhost:3000.)
36
37
1. Open new terminal window
38
+
1. Run `yarn build-dev` from project root. (This command sets up a development environment that keeps an eye on any file changes. When a file is updated, it auto-builds using the latest code.)
39
+
40
+
You can run `yarn test` to execute the test suite and linters. To help you develop the component we’ve set up some tests that cover the basic functionality (can be found in `/tests`). Even though we’re big fans of testing, this only covers a small piece of the component. We highly recommend you add tests when you’re adding new functionality.
41
+
37
42
1. After each JS change run `yarn build:js` in project root
38
43
1. After each SCSS change run `yarn run css:dev && yarn run css:modules:dev` in project root
0 commit comments