npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cookie-talk

v1.1.0

Published

A lightweight message-exchange protocol for window to window communication on same domain.

Downloads

2

Readme

cookie-talk

A lightweight message-exchange protocol for window to window communication on same domain.

Example

In this example we're going to create 2 html files that are to be open in to browser windows/tabs on the same domain name.

Whatever you type in each window appears in the other window. Messages are sent through channels. Each message is destoryed after being read.

First file:

<!DOCTYPE html>
<html>

	<head>
		<meta charset="utf-8">
		<title>Window 1</title>
		<script src="cookie-talk.min.js"></script>
	</head>
	<body>
		<div>
		Write Here:
		<textarea id="input"></textarea>
		</div>
		<hr>
		<div>
		Read here:
		<textarea id="output"></textarea>
		</dive>
	</body>
	<script>
		var ct = cookieTalk.storage;
		var channel1 = new ct('channel1');

		var editor = document.getElementById('input');
		editor.addEventListener('keyup', function(e) {
			channel1.send(editor.value, function() {
				//console.log('sent');
			});
		});

		var channel2 = new ct('channel2');
		var monitor = document.getElementById('output');
		channel2.onMessage(function(message) {
			monitor.value = message;
		})
	</script>
</html>

And second file

<!DOCTYPE html>
<html>

	<head>
		<meta charset="utf-8">
		<title>Window 2</title>
		<script src="cookie-talk.min.js"></script>
	</head>
	<body>
		<div>
		Read here:
		<textarea id="output"></textarea>
		</dive>
		<hr>
		<div>
		Write Here:
		<textarea id="input"></textarea>
		</div>
	</body>
	<script>

		var ct = cookieTalk.factory();
		var channel1 = new ct('channel1');

		var monitor = document.getElementById('output');
		channel1.onMessage(function(message) {
			monitor.value = message;
		})

		var channel2 = new ct('channel2');
		var editor = document.getElementById('input');
		editor.addEventListener('keyup', function(e) {
			channel2.send(editor.value, function() {
			//	console.log('Sent!');
			});
		});
	</script>

</html>

Make sure you have cookie-talk.min.js readable.

Also make sure your document has: <meta charset="utf-8"> in headers otherwise the minified .js does not work.