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

v0.4.0

Published

Create symlinks in your project, usually during a build process.

Downloads

478

Readme

grunt-symlink

Automate the creation of project symlinks. This is especially useful as part of a build process, where you often want to symlink to large media folders rather than include them in the build.

For example say you have a videos folder you'd like to exclude from your requirejs build because including it makes the build take forever. No problem, use symlinks instead. But creating these symlinks manually every time you run your build would be a pain. Let grunt-symlink handle it.

Getting Started

Install this grunt plugin next to your project's Gruntfile with: npm install grunt-symlink

Then add this line to your project's Gruntfile:

grunt.loadNpmTasks('grunt-symlink');

Documentation

In your Gruntfile add:

symlink: {
  links: [
    { link: 'path/to/new/symlink', to: '../path/to/original', type: 'dir'}
  ]
}

Important: link is relative to your project's root directory, but to is relative to link. For example:

symlinks: {
  links: [
    { link: 'frontend-build/videos', to '../videos'}
  ]
}

So in this case grunt-symlink will create a new symlink at myproject/frontend-build/videos that points to myproject/videos, because to in this case is relative to the frontend-build directory.

type can either be dir, file (default), or junction. See Node docs on symlinks.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Test your code using grunt.

License

Copyright (c) 2012 Dave Geddes
Licensed under the MIT license.