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-livereload

v0.1.3

Published

Refresh your CSS (or page) with each save via LiveReload.

Downloads

1,681

Readme

grunt-livereload

Refresh your CSS (or page) with each save via LiveReload.

Getting Started

First, install this grunt plugin next to your project's grunt.js gruntfile with: npm install grunt-livereload

Second, add this line to your project's grunt.js gruntfile:

grunt.loadNpmTasks('grunt-livereload');

Documentation

Third, have livereload monitor changes to browser-accessible resources. This part is crucial, as CSS, if specified correctly, can be reloaded without refreshing the entire page.

// grunt.js
{
  ...
  livereload  : {
    options   : {
      base    : 'public',
    },
    files     : ['public/**/*']
  }
  ...
}

In this example, public/css/app.css will trigger a reload of the css/app.css resource only, while public/index.html will cause a full page refresh.

Finally, ensure your watch task doesn't process CSS at the same time it processes HTML, JS, and other resources that are being monitored:

// grunt.js
{
  watch: {
    somecss: {
      files: '**/*.css',
      tasks: ['copy:somecss']
    },
    js: {
      files: '**/*.js',
      tasks: ['concat']
    }
  }
}

Many people watch everything and run their build process each time. This is unecessarily slow and prevents LiveReload from being able to see when only the .css has changed. So, it's recommended that you watch different types of files and perform only what's necessary to rebuild those.

This way, CSS is copied/processed alone and LiveReload will seamlessly replace the styles in your page without refreshing the whole browser.

Changelog

v0.1.0

  • Initial release

License

Copyright (c) 2013 Eric Clemmons Licensed under the MIT license.