@momentum-ui/design-tokens - npm Package Compare versions

Comparing version 0.0.3 to 0.0.4

package.json

@@ -5,3 +5,3 @@ {
   "description": "See [documentation on Confluence](https://confluence-eng-gpk2.cisco.com/conf/display/~pauwitty/Token+proposal)",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "main": "./dist/index.css",
@@ -34,3 +34,5 @@ "devDependencies": {
   },
-  "files": ["dist/**"]
+  "files": [
+    "dist/**"
+  ]
 }

README.md

@@ -18,12 +18,22 @@ # token-proposal
   --colorFormat=[hex|rgba]    What color format to use in the output.
-       rgba -> rgba(244,233,20,0.8)
-       hex  -> #RRGGBBAA (or would be if someone fixes it)
+       rgba   -> rgba(244,233,20,0.8)
+       object -> { "r": 244, "g": 233, "b": 20, "a": 0.8 }
+       hex    -> #RRGGBBAA
+       names  -> red-05
   --sizeUnit=[px|pt|rem]      What unit to use for sizes in the output.
-       px   -> pixels (matching that on Figma)
-       pt   -> points (pixels * 0.75)
-       rem  -> root em, used on web to create sizes relative to user font size
+       px    -> pixels (matching that on Figma)
+       pt    -> points (pixels * 0.75)
+       rem   -> root em, used on web to create sizes relative to user font size
+  --componentGroups           Group tokens by component
+  --omitThemeTokens           Removes theme tokens from the generated file
+  --fileFormat=[css|json]     What format to use for the output files
   --platform=PLATFORM         Which platform to generate for.
        web
-       desktop
+       qt
+       macos
+       ios
+       android
+  --toStdOut                  Output to std out instead of writing to files
 
 ```
+Tokens for individual components go in the components folder. If components are needed on only one platform, they should go in e.g. platformcomponents/ios/component_name.json. It's also possible to add platformcomponents/mobile/component_name.json which applies on both ios and android, or platformcomponents/desktop/component_name.json, for both macos and qt.

New 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

Fixed alerts

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

Improved metrics

Total package byte prevSize

378758

increased by26.59%

Lines of code

6274

increased by26.9%

Number of lines in readme file

39

increased by34.48%

No dependency changes