@invisionag/injixo-tokens - npm Package Compare versions

Comparing version 1.1.8 to 1.1.10

package.json

 {
   "name": "@invisionag/injixo-tokens",
-  "version": "1.1.8",
+  "version": "1.1.10",
   "description": "injixo Design Tokens",
@@ -31,14 +31,14 @@ "main": "index.js",
   "devDependencies": {
-    "@invisionag/eslint-config-ivx": "^4.4.0",
-    "@invisionag/prettier-config-ivx": "^2.0.0",
-    "eslint": "^6.8.0",
-    "eslint-config-airbnb": "^18.1.0",
-    "execa": "^4.0.0",
-    "lodash": "^4.17.11",
-    "prettier": "^2.0.2",
-    "rollup": "^2.2.0",
-    "style-dictionary": "^2.8.0",
-    "typescript": "^3.5.1"
+    "@invisionag/eslint-config-ivx": "^5.0.9",
+    "@invisionag/prettier-config-ivx": "^2.0.11",
+    "eslint": "^7.7.0",
+    "eslint-config-airbnb": "^18.2.0",
+    "execa": "^4.0.3",
+    "lodash": "^4.17.20",
+    "prettier": "^2.1.1",
+    "rollup": "^2.26.5",
+    "style-dictionary": "^2.10.1",
+    "typescript": "^4.0.2"
   },
   "prettier": "@invisionag/prettier-config-ivx"
 }

README.md

@@ -38,5 +38,4 @@ # injixo-tokens
 
-- Execute `yarn publish` inside your terminal
 - Update version number accordingly ([semver](https://semver.org/))
-- Check if package was published successfully by navigating to https://www.npmjs.com/package/@invisionag/injixo-tokens (might take a few minutes to update there)
+- After merging to master, CI will automatically publish the new version to the npm registry. Check if this worked by navigating to https://www.npmjs.com/package/@invisionag/injixo-tokens (might take a few minutes to update there)
 
@@ -52,7 +51,5 @@ ### Publish Gem
 - Update gems with
-  - `cd gem`
-  - `bundle update`
+  - `cd gem && bundle update`
 - Update node modules with
-  - `npm update`
-  - `npm outdated`
-  - (see output of latter command for further instructions)
+  - `yarn upgrade` to update minor and patch versions
+  - `yarn upgrade-interactive --latest` to interactively update major releases

New alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Worsened metrics

Total package byte prevSize

3258

decreased by-98.22%

Number of package files

3

decreased by-70%

Lines of code

0

decreased by-100%

Number of lines in readme file

54

decreased by-5.26%

Number of medium supply chain risk alerts

3

increased by200%

No dependency changes