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
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,25 +19,25 @@ If you would like to contribute by fixing an open issue or developing a new feat
19
19
1. Fork this repository
20
20
2. Create a new feature branch based off the `main` branch
21
21
3. Follow the [Core lib](#core-lib) and/or the [docs](#docs) guide below and come back to this once done
22
-
4. Run `yarn run prettier` to format the code
22
+
4. Run `pnpm run prettier` to format the code
23
23
5. Git stage your required changes and commit (review the commit guidelines below)
24
24
6. Submit the PR for review
25
25
26
26
### Core lib
27
27
28
-
1. Install dependencies by running `yarn`. We use [version 1](https://classic.yarnpkg.com/lang/en/docs/install) of yarn
28
+
1. Install dependencies by running `pnpm`.
29
29
2. Create failing tests for your fix or new feature in the `tests` folder
30
30
3. Implement your changes
31
-
4. Build the library `yarn run build`_(Pro-tip: `yarn run build-watch` runs the build in watch mode)_
32
-
5. Run the tests and ensure that they pass._(Pro-tip: `yarn test:dev` runs the test in watch mode)_
33
-
6. You can use `yarn link` or `yalc` to sym-link this package and test it locally on your own project. Alternatively, you may use CodeSandbox CI's canary releases to test the changes in your own project (requires a PR to be created first)
31
+
4. Build the library `pnpm run build`_(Pro-tip: `pnpm run build-watch` runs the build in watch mode)_
32
+
5. Run the tests and ensure that they pass.
33
+
6. You can use `pnpm link` or `yalc` to sym-link this package and test it locally on your own project. Alternatively, you may use CodeSandbox CI's canary releases to test the changes in your own project (requires a PR to be created first)
34
34
7. Follow step 4 and onwards from the [general](#general) guide above to bring it to the finish line
35
35
36
36
### Docs
37
37
38
38
1. Navigate to the `website` folder. Eg. `cd website`
39
-
2. Install dependencies by running `yarn` in the `website` folder We use [version 1](https://classic.yarnpkg.com/lang/en/docs/install) of yarn
40
-
3. Run `yarn dev` to start the dev server
39
+
2. Install dependencies by running `pnpm` in the `website` folder
40
+
3. Run `pnpm dev` to start the dev server
41
41
4. Navigate to [`http://localhost:9000`](http://localhost:9000) to view the docs
42
42
5. Navigate to the `docs` folder and make necessary changes to the docs
43
43
6. Add your changes to the docs and see them live reloaded in the browser
@@ -49,7 +49,7 @@ We follow the [conventional commit spec](https://www.conventionalcommits.org/en/
49
49
50
50
Your commit type must be one of the following:
51
51
52
-
-**build**: Changes that affect the build system or external dependencies (example scopes: yarn, npm, rollup, etc.)
52
+
-**build**: Changes that affect the build system or external dependencies (example scopes: pnpm, npm, rollup, etc.)
53
53
-**ci**: Changes to our CI configuration files and scripts (example scopes: GitHub Actions)
@@ -370,7 +370,7 @@ This guarantees that a single effect will be used regardless of how many calls t
370
370
371
371
The same guarantee can be achieved with the useEffect hook if you ensure that the useEffect is idempotent.
372
372
373
-
atomEffects are distinguished from useEffect in a few other ways. They can directly react to atom state changes, are resistent to infinite loops, and can be mounted conditionally.
373
+
atomEffects are distinguished from useEffect in a few other ways. They can directly react to atom state changes, are resistant to infinite loops, and can be mounted conditionally.
Copy file name to clipboardExpand all lines: docs/extensions/immer.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ npm i immer jotai-immer
15
15
16
16
## atomWithImmer
17
17
18
-
`atomWithImmer` creates a new atom similar to the regular [`atom`](../core/atom.mdx)[atom]with a different `writeFunction`. In this bundle, we don't have read-only atoms, because the point of these functions is the immer produce(mutability) function.
18
+
`atomWithImmer` creates a new atom similar to the regular [`atom`](../core/atom.mdx) with a different `writeFunction`. In this bundle, we don't have read-only atoms, because the point of these functions is the immer produce(mutability) function.
19
19
The signature of writeFunction is `(get, set, update: (draft: Draft<Value>) => void) => void`.
0 commit comments