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

intern-dev

v0.3.4

Published

Development support scripts for Intern projects.

Downloads

7

Readme

intern-dev

Support scripts for Intern and its sub-projects

Usage

Include this project in devDependencies in your Intern component's package.json, then add the desired scripts to scripts in package.json. For example:

"scripts": {
	"build": "intern-dev-build",
	"clean": "intern-dev-clean",
	"lint": "intern-dev-lint",
	"release": "intern-dev-release",
	"test": "intenr-dev-clean && intern-dev-build && intern-dev-test",
	"watch": "intern-dev-watch"
}

Configuration

Components should generally try to follow the conventions used by this package (standard tslint, sources in src, test config in tests/intern.js, etc.), in which case no configuration is required. However, limited configuration is supported through the internDev property in your project's package.json.

"internDev": {
	// Patterns to ignore
	"ignore": [ "ignore", "glob", "patterns" ],
	"resources": {
		// Arrays of patterns to copy for a build, keyed by destination path
		"_build": [
			"patterns",
			{ base: "src/stuff", pattern: "to" },
			"copy"
		]
	},
	// Path to custom test config
	"testConfig": "tests/custom.config.js"
}

Note that all paths and path patterns are relative to the project root.