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

mock-cookie

v0.3.2

Published

### Status | Branch | Status | | ------------- |:-------------:| | master | [![Build Status](https://travis-ci.org/Aspera/mock-cookie.png?branch=master)](https://travis-ci.org/Aspera/mock-cookie) |

Downloads

488

Readme

Mock Cookie

Status

| Branch | Status | | ------------- |:-------------:| | master | Build Status |

A mocked version of the "standard" cookie used in browsers. It doesn't include options for path, domain, secure or http only at the moment.

The primary purpose of its creation was for unit tests. Having to clear out cookies for unit tests was tedious and not always reliable/accurate. Sometimes in some tests, document.cookie wasn't even available. This mock version helps ensure clean, consistent results.

Installation

The best way is to use bower to manage the process:

bower install --save-dev mock-cookie

Usage

Assign a new version of the cookie to the object you want to represent it, usually document.

In unit tests:

window = require('path/to/mock-cookie.js').Document;
document = new window();
document.cookie = 'value to add';

From there, use document.cookie as you normally would to test your application.

In code:

<script src='path/to/mock-cookie.js'></script>
<script>
  myDoc = new window.Document();
  myDoc.cookie = 'value to add';
</script>

By using myDoc.cookie instead of document.cookie in your application, you can keep the original functionality to test against. If you really want to override document.cookie for some reason:

<script src='path/to/mock-cookie.js'></script>
<script>
  document.cookie = (new window.Document()).cookie;
  document.cookie = 'value to add';
</script>

Future Plans

  • Max-age support needs to be added.
  • Path: Support for this woud depend on window.location.pathname being mocked out as well.
  • Domain: Similiar to path but with window.location.{host|hostname|origin}
  • Secure: Similiar to path but with window.location.protocol
  • Http-only: Not sure how to mock this out since JS wouldn't have access to the cookie. That could probably be the test