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: installers/npm/PUBLISHING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Here's how to update the `npm` installer.
5
5
## 0. Overview
6
6
7
7
- There is one _main npm package_ called `elm`.
8
-
- Then there is one _binary npm package_ for each platform, called for example `@evancz/elm_darwin_arm64`.
8
+
- Then there is one _binary npm package_ for each platform, called for example `@elm_binaries/darwin_arm64`.
9
9
10
10
The binary packages declare which OS and CPU they are compatible with. For example:
11
11
@@ -17,9 +17,9 @@ The binary packages declare which OS and CPU they are compatible with. For examp
17
17
The main npm package depend on the binary packages via [optional dependencies](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#optionaldependencies):
18
18
19
19
```json
20
-
"@evancz/elm_darwin_arm64": "0.19.1-0",
21
-
"@evancz/elm_darwin_x64": "0.19.1-0",
22
-
"@evancz/elm_linux_arm64": "0.19.1-0",
20
+
"@elm_binaries/darwin_arm64": "0.19.1-0",
21
+
"@elm_binaries/darwin_x64": "0.19.1-0",
22
+
"@elm_binaries/linux_arm64": "0.19.1-0",
23
23
...
24
24
```
25
25
@@ -60,7 +60,7 @@ Repeat this for all the packages mentioned in the previous section. This uses `p
60
60
2. Double-check that you put the right binary in the right package: `file elm`
61
61
3. Double-check that the file is executable: `ls -l elm`
62
62
4. In `package.json` of the binary package, bump the version for example to `"0.19.1-2"`.
63
-
5. In `package.json` of the main npm package, update `"optionalDependencies"` to point to the bumped version. For example: `"@evancz/elm_darwin_arm64": "0.19.1-2"`
63
+
5. In `package.json` of the main npm package, update `"optionalDependencies"` to point to the bumped version. For example: `"@elm_binaries/darwin_arm64": "0.19.1-2"`
64
64
6. Publish the package: `npm publish --access=public`
65
65
66
66
`--access=public` is needed because scoped packages are private by default.
0 commit comments