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: fern/products/sdks/overview/typescript/publishing-to-npm.mdx
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,12 @@ title: Publishing to npm
3
3
description: How to publish the Fern TypeScript SDK to npm.
4
4
---
5
5
6
-
Publish your public-facing Fern TypeScript SDK to the [npm
7
-
registry](https://www.npmjs.com/). After following the steps on this page,
8
-
you'll have a versioned package published on npm.
6
+
Publish your public-facing Fern TypeScript SDK to the [npm registry](https://www.npmjs.com/). After following the steps on this page, you'll have a versioned package published on npm.
7
+
8
+
Deep made a change!!!
9
9
10
10
<Frame>
11
-
<imgsrc="assets/npm-packages.png"alt="Versioned package published on npm" />
11
+
<imgsrc="file:3afaf258-4304-4245-8cef-fb9bd4909581"alt="Versioned package published on npm" />
12
12
</Frame>
13
13
14
14
<Info>
@@ -35,7 +35,7 @@ you'll have a versioned package published on npm.
@@ -177,7 +177,7 @@ Set up a release workflow via [GitHub Actions](https://docs.github.com/en/action
177
177
Open your Fern repository in GitHub. Click on the **Settings** tab in your repository. Then, under the **Security** section, open **Secrets and variables** > **Actions**.
0 commit comments