@aller/blink-labrador - npm Package Compare versions

		@@ -237,3 +237,4 @@ 'use strict';
		sourceAgnosticCreativeId: event.sourceAgnosticCreativeId,
		sourceAgnosticLineItemId: event.sourceAgnosticLineItemId
		sourceAgnosticLineItemId: event.sourceAgnosticLineItemId,
		bidder: event.slot.getTargeting('hb_bidder').join(',')
		});
		@@ -240,0 +241,0 @@ });

package.json

		{
		"name": "@aller/blink-labrador",
		"version": "0.2.3",
		"version": "0.3.0",
		"description": "Library for using blink on Labrador",
		@@ -52,3 +52,3 @@ "main": "lib/main.js",
		"dependencies": {
		"@aller/blink": "1.0.0",
		"@aller/blink": "1.1.0",
		"@soldotno/aller-in-view": "^3.0.2"
		@@ -55,0 +55,0 @@ },

README.md

		@@ -18,2 +18,3 @@ # blink-labrador
		const tracker = new BlinkLabrador();
		tracker.trackPageload();
		tracker.trackAdInscreen0('.adunit');
		@@ -29,1 +30,13 @@ tracker.trackAdInscreen('.adunit');
		```

		## Releasing

		1. Make sure that the latest changes is merged into master via a pull request

		2. If it is a bugfix run `npm version patch`, if it is a new feature run `npm version minor`, and if where is a breaking change run `npm version major`. We use semantic versionion, and 1.0.0 is no holy grail for "finished" software, and we should not be afraid of releasing major versions.

		3. Publish it by running `npm publish`. This will transpile all files and publish them to npm.

		4. Push the release to GitHub.

		5. It is greatly apprecieated if you write a summary of the release on GitHub releases. You do that by opening the releases overview page on GitHub, clicking your newly pushed release, and then clicking the "Edit tag" button.

New alerts