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

v1.1.0

Published

Liquidjs for your grunt tasks.

Downloads

5

Readme

grunt-liquify

A Grunt task to process Liquid using liquidjs. Use it to add Liquid magic to your scripts and css assets.

Installation

npm install grunt-liquify

Examples

Inside Gruntfile.js.

module.exports = function(grunt) {
  grunt.initConfig({
    liquify: {
      options: {
        dataDirectory: 'data',
        data: {foo: 'bar'}
      },
      example1: {
        // liquify and overwrite existing file(s)
        src: 'dist/*.js'
      },
      example2: {
        // liquify and output to a new file
        src: 'dist/script.js',
        dest: 'dist/script.done.js'
      },
      example3: {
        // Liquify src directory and copy to dist
        cwd: 'src',
        src: '**/*.js',
        dest: 'dist',
        expand: true
      }
    }
  })
  grunt.loadNpmTasks('grunt-liquify');
  grunt.registerTask('default', function() {
    grunt.task.run([
      'liquify'
    ])
  })
}

Options can be defined per task

module.exports = function(grunt) {
  grunt.initConfig({
    liquify: {
      example: {
        options: {data:{foo: 'bar'}},
        src: 'dist/*.js'
      }
  });
  grunt.loadNpmTasks('grunt-liquify');
  grunt.registerTask('default', function() {
    grunt.task.run([
      'liquify'
    ])
  })
}

Options

| Tag | type | default | description | |-------------- |-------: |--------- |----------------------------------------------------------------------------------------------------------- | | dataDirectory | string | null | optional path to a directory that contains js data to be imported using the node require method. | | data | object | null | optional object to pass to liquid. This data has a higher priority than dataDirectory. |

Data

All data is deep merged and must be compatible with the node require method. The filename is used as the object key. The final data object is then passed to all liquid templates.

For example this data directory:

data
  ├── config.js
  └── foo.js

will produce

{
  config: {},
  foo: {}
}

Test

Run npm install in /test then run grunt.