@loophq/design-system - npm Package Compare versions

Comparing version 2.0.0-beta.15 to 2.0.0-beta.16

package.json

 {
   "name": "@loophq/design-system",
-  "version": "2.0.0-beta.15",
+  "version": "2.0.0-beta.16",
   "homepage": "https://loop-design-system.netlify.app/",
@@ -33,12 +33,9 @@ "files": [
     "@babel/core": "7.9.0",
-    "@storybook/addon-a11y": "6.2.9",
-    "@storybook/addon-actions": "6.2.9",
-    "@storybook/addon-console": "1.2.3",
-    "@storybook/addon-docs": "6.2.9",
-    "@storybook/addon-knobs": "6.2.9",
-    "@storybook/addon-links": "6.2.9",
-    "@storybook/addon-storysource": "6.2.9",
-    "@storybook/addon-viewport": "6.2.9",
-    "@storybook/addons": "6.2.9",
-    "@storybook/vue": "6.2.9",
+    "@storybook/addon-a11y": "^6.5.9",
+    "@storybook/addon-console": "^1.2.3",
+    "@storybook/addon-essentials": "^6.5.9",
+    "@storybook/addon-links": "^6.5.9",
+    "@storybook/addon-storysource": "^6.5.9",
+    "@storybook/addons": "^6.5.9",
+    "@storybook/vue": "^6.5.9",
     "@testing-library/user-event": "10.4.0",
@@ -45,0 +42,0 @@ "@testing-library/vue": "5.0.3",

README.md

@@ -61,3 +61,3 @@ # Loop design system
 
-Makes sure to push the updates that npm makes when publishing to your release branch before merging into master.
+Makes sure to push the updates that npm makes when publishing to your release branch before merging into main.
 
@@ -72,3 +72,3 @@ ## Compiles storybook
 0. If this is your first time releasing, ask in the engineering team channel to be added to the loop npm organization. Make sure you log in to npm in your terminal as well.
-1. On your machine, check out the branch you'd like to release. This can either be a feature branch or a release branch if you have multiple features to package together as a release. This branch should be PRed into `master` and be approved by a peer before releasing.
+1. On your machine, check out the branch you'd like to release. This can either be a feature branch or a release branch if you have multiple features to package together as a release. This branch should be PRed into `main` and be approved by a peer before releasing.
 2. Compile the component library
@@ -81,3 +81,3 @@ ```
 3. Figure out the version number this release will be. We follow [SemVer](https://semver.org/), and the general rule of thumb is that if you're adding new components, bump the minor version, everything else should just bump the patch version. Major versions bumps are rare and should be a team decision.
-4. Publish the library to npm. **Make sure you are on the branch you intend to release, this will modify your `package.json` and you MUST be on a non-`master` branch for this to be mergeable.**
+4. Publish the library to npm. **Make sure you are on the branch you intend to release, this will modify your `package.json` and you MUST be on a non-`main` branch for this to be mergeable.**
     ```
@@ -87,2 +87,2 @@ npm run library:publish -- <version>
 5. Push all changes the build and release scripts made to Github.
-6. In Github, merge the release branch into master.
+6. In Github, merge the release branch into main.

No alert changes

Improved metrics

Total package byte prevSize

261380

increased by8.91%

Dev dependency count

27

decreased by-10%

Lines of code

3595

increased by5.74%

No dependency changes