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

can-simple-window

v0.1.0

Published

A very light-weight execution context (window) wrapper for can-simple-dom

Downloads

222

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ryanwhealeryanwheale

Keywords

Readme

can-simple-window

A very simple, light-weight execution context (eg. browser window) which wraps around can-simple-dom. This module allows for both jQuery, CanJS, ReactJS, and other scripts to be loaded in a NodeJS environment by creating a faux browser window in which the scripts are executed. A very basic implementation of the DOM API is provided by can-simple-dom.

The API was designed to be a drop in replacement for very simple jsdom implementations. Please note that this does not support the entire jsdom API and that can-simple-dom is a very limited implementation of the WHATWG DOM specification. If you are looking for an environment which more closely resembles a real browser, please use jsdom - it is a wonderful library.

##simpleWindow.env(html [, scripts], callback); Replacement for jsdom.env

var simpleWindow = require('can-simple-window');

simpleWindow.env(
	'<h1>Hello World!</h1><span class="foo"><b>BAR!</b></span>',
	['http://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js',
	'http://canjs.com/release/2.2.9/can.jquery.min.js'],
	function (err, window) {
	   if (err) throw new Error(err);
	   
		window.$('h1').text(); //-> Hello World!
		window.$('.foo').html(); //-> <b>BAR!</b>
		window.can; //-> Reference to CanJS object
	}
);

Differences from jsdom

  • You can only pass HTML in the first parameter (no URLs or file paths)

    • The html passed in is only attached to the <body> - no <head> code will be processed.
    • <script>, <img>, <link>, <frame>, and <iframe> sources will not be loaded or processed.

  • There is no config object - so the following are invalid:

    simpleWindow.env({ config_object });
simpleWindow.env("<b>foo</b>", 'script.js', { config_object }, ...);

  • There are no lifecycle events for created or onLoad

##simpleWindow.document(html); Replacement for jsdom.jsdom

var simpleWindow = require('can-simple-window');

var document = simpleWindow.document('<h1>Hello World!</h1><span class="foo"><b>BAR!</b></span>');
document.getElementsByTagName('h1'); //-> [ H1 DOM Element ]
document.getElementsByClassName("foo"); //-> [ SPAN.foo DOM Element ]

Differences from jsdom

  • The html passed in is only attached to the <body> - no <head> code will be processed.
  • <script>, <img>, <link>, <frame>, and <iframe> sources will not be loaded.
  • There is no options parameter implemented.