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
There may be some scenarios where we want to test out new components within the project that will actually consume it prior to releasing a new version on NPM.
52
+
##Beta
53
+
Sometimes it may be necessary to test your consuming application prior to creating a release. For example, you just added a new component and want to test it out in the application to make sure everything looks and works as expected.
54
54
55
-
For this we can use [gitpkg](https://gitpkg.vercel.app/)as a proxy to point to our dev branch:
55
+
For this we can use NPM's "beta" tags. This will allow the compiled code to be added as a dependency from NPM, but will not map to the "latest" release for production.
56
56
57
-
#### Step 1: Update react-components package.json
58
-
Update all package.json file to use gitpkg instead of NPM version:
57
+
Let's say the current version number is "0.5.15". You can update all of the versions in `package.json` to "0.5.16-beta.0" and publish the package(s) to NPM via:
Run `yarn install` and commit the changes to your branch.
79
-
80
-
❗Make sure to include the `scripts` parameter in order to build the dependency in your consuming project.
81
-
82
-
❗Make sure to revert these changes prior to creating an NPM release.
83
-
84
-
#### Step 2: Update your projects package.json
85
-
Update your projects package.json file to use gitpkg instead of the NPM version. You'll also want to add the package's dependencies as dependencies in your project. For example: If your project uses `@performant-software/semantic-components`, you'll also want to add `@performant-software/shared` and `@performant-software/webpack-config` as dependencies to your project temporarily.
0 commit comments