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

dep-linker

v1.0.24

Published

Copy your npm dependencies to serve them to the front-end.

Downloads

28

Readme

Dependencies Linker

Link your npm dependencies to serve them to the front-end.

Automatically link your project's dependency files to a folder like public/scripts so that you can serve them to the front end.

Install

npm install --save-dev dep-linker

Use


var depLinker = require('dep-linker');
depLinker.linkDependenciesTo('./public/scripts')
  .then(() => console.log('Finished.'));
  // Done! All your dependencies ready to be served to the front-end

dev-dependencies are not linked.

Task runners

There still isn't a specific wrapper for any task runner, but given that this is just javascript for now you can use it like this and it will work like a charm:

Gulp

var depLinker = require('dep-linker');

gulp.task('link-dependencies', function () {
  return depLinker.linkDependenciesTo('./public/scripts');
});

Grunt

var depLinker = require('dep-linker');

grunt.task.registerTask('link-dependencies', 'Copy npm dependencies', function () {
    var done = this.async(); // <-- must be async
    return depLinker.linkDependenciesTo('public/scripts')
      .then(() => done())
      .catch(() => done());
});

Options

Set root folder

dep-linker gets your dependencies from your package.json which is in your project's root folder. If the script is not being run from the root folder, specify the path to it:

var depLinker = require('dep-linker');
depLinker.setRoot('../../');