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 🙏

© 2025 – Pkg Stats / Ryan Hefner

single-page-react

v0.0.2

Published

Lightweight, straightforward plugin for creating single page apps with React

Downloads

18

Readme

single-page-react

A lightweight, straightforward plugin for creating single page apps with ReactJS.

##Concept

Making a single page app built with React doesn't need to be complicated. There's no need to bring in Backbone and Underscore if you don't want to.

##What single-page-react does

single-page-react chooses one of your React components and inserts it into the DOM.

#####Which React component is inserted into the DOM?

The one whose route attribute matches the current URL hash.

#####Where in the DOM will my React component by inserted?

Into the element whose id is stored in the React.Router.routedElement variable. By default, this is document.body.

#####What happens when I change the page's hash?

single-page-react will replace the React component inside of routedElement with the React component whose route attribute matches the hash. Take advantage of React virtual DOM diffing by reusing components; this way re-routing can be almost instantaneous!

#####Can I pass variables to my routedElement?

Yes. The key-value pairs in the URL query are given to your React component via the this.props variable.

##Example

home.jsx /** @jsx React.DOM */

var Home = React.createClass({
	render: function() {
		return (
			<div>
				{this.props.prop1}
			</div>
		);
	},

  //When the URL hash is '#home', mount this component into the routedElement.
	route: 'home' 
});

index.html

<html>
	<head>
		
		<!-- Bring in React and single-page-react dependencies as globals -->
		<script src="//cdnjs.cloudflare.com/ajax/libs/react/0.11.1/react.js"></script>
		<script src="//cdnjs.cloudflare.com/ajax/libs/react/0.11.1/JSXTransformer.js"></script>
		<script src="single-page-react.js"></script>
	  
		<!-- Set which DOM element to insert React components into -->
		<script>
  			React.Router.routedElement = document.body //or whatever element you prefer
    </script>  

    <!-- Bring in the home react component -->
		<script src="home.jsx" type="text/jsx"></script>
		
	</head>

	<body>
		This text is replaced by routed React components. For example, when the url 
		ends with #home?prop1=customValue, this text will be replaced by a div whose
		content is 'customValue'
	</body>
</html>