oss-mariner - npm Package Compare versions

Comparing version 0.1.0 to 0.1.1

package.json

		{
		"name": "oss-mariner",
		"version": "0.1.0",
		"version": "0.1.1",
		"description": "A node.js library for analyzing open source library dependencies",
		"main": "dist/mariner.js",
		"types": "dist/mariner.d.ts",
		"main": "dist/dependency-details-retriever.js",
		"types": "dist/dependency-details-retriever.d.ts",
		"author": "",
		@@ -8,0 +8,0 @@ "license": "Apache-2.0",

README.md

		@@ -73,2 +73,9 @@ # Mariner

		## Local testing of the npm packaging

		You should have local copies of both the oss-mariner project and the project that will include it.
		In the oss-mariner project, run ```npm link```. This will "publish" oss-mariner locally on your
		computer. Then in the other project, run ```npm link oss-mariner```.
		This will replace the public npm version of oss-mariner with your local copy.

		## Project Maintainers
		@@ -80,4 +87,6 @@

		1. If you are a maintainer, you can follow these steps to publish a new version of the package:
		If you are a maintainer, you can follow these steps to publish a new version of the package:
		1. Be sure the version number in package.json is correct
		1. Run ```npm install``` to update package-lock.json
		1. Run ```npm run build``` and ```npm run lint``` to make sure there are no errors
		1. Login to npm if you haven’t already: npm login
		@@ -84,0 +93,0 @@ 1. Do a dry run to make sure the package looks good: npm publish --dry-run

New alerts