component-simple-slider - npm Package Compare versions

Comparing version 0.1.0 to 0.1.1

package.json

 {
   "name": "component-simple-slider",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "A simple slider component as a Custom Element",
   "main": "src/index.js",
-  "files": ["./src"],
+  "files": [
+    "./src"
+  ],
   "repository": "[e-mail]:ProjectEvergreen/component-simple-slider.git",
@@ -17,6 +19,7 @@ "author": "Owen Buckley <[e-mail]>",
   },
-  "dependencies": {
+  "peerDependencies": {
     "@polymer/lit-element": "^0.5.2"
   },
   "devDependencies": {
+    "@polymer/lit-element": "^0.5.2",
     "@polymer/test-fixture": "^3.0.0-pre.21",
@@ -39,2 +42,2 @@ "css-loader": "^0.28.11",
   }
-}
+}

README.md

@@ -34,2 +34,14 @@ # component-simple-slider
 - For a dev server running a "reference app", run `yarn develop`
-- To run unit tests, run `yarn test`
+- To run unit tests, run `yarn test`
+
+## Publishing
+> Follow [these steps](https://docs.npmjs.com/getting-started/publishing-npm-packages) for authenticating with **npm**.
+
+Here are the basic steps to follow for publishing a new release
+1. Make sure all commits are in `master`
+1. Make sure there are no changes in your working directory by running `git status`
+1. Set the version by running `npm version <major|minor|patch>`
+1. Pubish to npm by running `npm publish`
+1. Tag and push up all changes with `git tag -a x.y.z -m "tagging x.y.z release"
+1. Create [release notes](https://github.com/ProjectEvergreen/component-simple-slider/releases) in GitHub
+1. Verify the release in the [npm registry](https://www.npmjs.com/package/component-simple-slider)

No alert changes

Improved metrics

Total package byte prevSize

17439

4.61%

Number of lines in readme file

46

35.29%

Worsened metrics

Dev dependency count

17

6.25%

Dependency changes

• - Removed

  @polymer/lit-element@^0.5.2