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
* chore(tooling): setup release pipeline
* chore: add validate PR title workflow to enforce semantic commits
* fix(pkg): use correct name for docs package
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
-71Lines changed: 0 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,74 +20,3 @@ Be sure your commit messages follow this specification: https://www.conventional
20
20
### Windows permission errors
21
21
22
22
Some Windows users may need to [enable developer mode](https://howtogeek.com/292914/what-is-developer-mode-in-windows-10) if experiencing `EPERM: operation not permitted, symlink` with Preconstruct. If this persists, you might be running on an unsupported drive/format. In which case, consider using [Docker](https://docs.docker.com/docker-for-windows).
23
-
24
-
### Duplicate `react` errors
25
-
26
-
React 16.8+ has global state to support its "hooks" feature, so you need to ensure only one copy of `react` exists in your program. Otherwise, you'll most likely see [this error](https://reactjs.org/warnings/invalid-hook-call-warning.html). Please try the following solutions, and let us know if it still doesn't work for you.
27
-
28
-
-**For `create-react-app` users:** Follow this guide: https://github.com/facebook/react/issues/13991#issuecomment-496383268
29
-
30
-
-**For `webpack` users:** Add an alias to `webpack.config.js` like this:
31
-
32
-
```js
33
-
alias: {
34
-
react:path.resolve('node_modules/react'),
35
-
}
36
-
```
37
-
38
-
-**For `gatsby` users:** Install `gatsby-plugin-alias-imports` and add this to your `gatsby-config.js` module:
39
-
```js
40
-
{
41
-
resolve:`gatsby-plugin-alias-imports`,
42
-
options: {
43
-
alias: {
44
-
react:path.resolve('node_modules/react'),
45
-
},
46
-
},
47
-
},
48
-
```
49
-
50
-
# Publishing
51
-
52
-
We use [`changesets`](https://github.com/atlassian/changesets) to publish our package now.
53
-
All our dependencies are fixed using ~ after [1414](https://github.com/pmndrs/react-spring/issues/1414) but luckily changesets will bump them for every minor version we release.
54
-
55
-
## Simple release
56
-
57
-
You want to release some new features that haven't been released yet:
58
-
59
-
```shell
60
-
yarn changeset:add
61
-
```
62
-
63
-
Follow the prompt to flag which packages need to update although with `react-spring` we keep all our packages at the same version.
64
-
65
-
Then you'll run:
66
-
67
-
```shell
68
-
yarn vers
69
-
```
70
-
71
-
This will update all the packages correctly according to what version you just set with the `add` script & possibly update the deps within those packages.
72
-
73
-
Finally:
74
-
75
-
```shell
76
-
yarn release
77
-
```
78
-
79
-
This will build the packages, publish them & push the tags to github to signify a new release. Please then update the `releases` on github & the changelog on `react-spring.io`
80
-
81
-
## Prerelease
82
-
83
-
Everything above applies but you must first run:
84
-
85
-
```shell
86
-
yarn changeset pre enter beta | alpha | next
87
-
```
88
-
89
-
If you find you're stuck in a prerelease and trying to do a Simple Release, try running:
0 commit comments