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

grunt-aem-watch

v1.0.9

Published

A simple plug-in to upload files to an active AEM instance, recommended for use with grunt-contrib-watch.

Downloads

4

Readme

grunt-aem-watch

aem-watch task

Usage

aem-watch: {
	localAuthor: {
		options: {
			server: 'author'
		},
		src: [
			'your/js/path/**/*.js',
			'your/css/path/**/*.css',
		]
	},
	localPublish: {
		options: {
			server: 'publish'
		},
		src: [
			'your/js/path/**/*.js',
			'your/css/path/**/*.css',
		]
	},
	qaAuthor: {
		options: {
			host: 'qa-author.mydomain.com',
			password: 'myqapassword',
			server: 'author',
			username: 'myqausername'
		},
		src: [
			'your/js/path/**/*.js',
			'your/css/path/**/*.css',
		]
	},
	qaPublish: {
		options: {
			host: 'qa-publish.mydomain.com',
			password: 'myqapassword',
			server: 'publish',
			username: 'myqausername'
		},
		src: [
			'your/js/path/**/*.js',
			'your/css/path/**/*.css',
		]
	}
}

... then your Grunt Watch configuration...

watch: {
	your_task: {
		files: <your file rules>,
		tasks: ['aem-watch:localAuthor', 'aem-watch:localPublish']
	}
}

Allowed Options

  • host - The host (without protocol or port) to call, defaults to 'localhost'
  • password - The password to use, defaults to 'admin'
  • port - The port to use, defaults to '4502' for 'author' and '4503' for 'publish'
  • server - Optional set of default configurations, either 'author' or 'publish'
  • target - The target path to use if not the same as the file location, e.g. if you need to prefix with '/etc/designs/your-design/' you would define that as your target
  • updateWindow - this allows you to specify, in seconds, how recently a file was updated to be eligible, defaults to 15
  • username - The username to use, defaults to 'admin'