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
* switch typedoc to using patched branch to fix anchors
* try again
* try again
* Update imports.md
* move website-only deps to website/package.json
* update main<->docs merge instructions in CONTRIBUTING.md
* fix potential confusion about docs<->main merge strategy
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Docs for the latest stable release live in a `docs` branch. The "Edit this page
29
29
branch so that the website can be improved in parallel with new feature work.
30
30
31
31
Docs changes for unreleased features are merged to `main` in the same PR which implements the feature, adds tests, etc.
32
-
When we release a new version, we merge `main`into`docs` and `docs` into `main`, unifying the two.
32
+
When we release a new version, we merge `main`with`docs`, unifying the two.
33
33
34
34
```shell
35
35
cd ./website
@@ -44,11 +44,14 @@ This site was used to generate the favicon from a high-res PNG export of the SVG
44
44
45
45
We publish using `np`: https://npm.im/np
46
46
47
-
1. Merge `docs` into `main`
47
+
1. Merge `docs` into `main` using a pull request, ensuring a consistent squash-merge
48
48
2. Rebuild the README (see instructions above, necessary because npmjs.com renders the readme)
49
49
3. Publish with `np`
50
50
4. Add changelog to the Github Release; match formatting from previous releases
51
-
5. Merge `main` into `docs` (this automatically rebuilds the website)
51
+
5. Move `docs` branch to head of `main`
52
+
- this rebuilds the website
53
+
-`git push --force origin main:docs`
54
+
- avoids merge messiness due to earlier squash-merge from `docs` to `main`
52
55
6. If tsconfig schema has changed, send a pull request to schemastore. [Example](https://github.com/SchemaStore/schemastore/pull/1208)
Copy file name to clipboardExpand all lines: website/docs/imports.md
+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 @@ Here is a brief comparison of the two.
15
15
16
16
## CommonJS
17
17
18
-
Transforming to CommonJS is typically simpler and more widely supported because it is older. You must remove or set [`"type": "commonjs"`](https://nodejs.org/api/packages.html#packages_type)in`package.json` and [`"module": "CommonJS"`](https://www.typescriptlang.org/tsconfig/#module) in `tsconfig.json`.
18
+
Transforming to CommonJS is typically simpler and more widely supported because it is older. You must remove [`"type": "module"`](https://nodejs.org/api/packages.html#packages_type)from`package.json` and set[`"module": "CommonJS"`](https://www.typescriptlang.org/tsconfig/#module) in `tsconfig.json`.
0 commit comments