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-bower-install-shopware

v0.2.2

Published

Inject your Bower dependencies right into your HTML from Grunt.

Downloads

5

Readme

grunt-bower-install

Inject your Bower dependencies right into your HTML from Grunt.

What is this?

Grunt is great.

Bower is great.

And now they work great together.

grunt-bower-install is a Grunt plug-in, which finds your components and injects them directly into the HTML file you specify.

Whether you're already using Bower and Grunt, or new to both, grunt-bower-install will be easy to plug in, as you will see in the steps below.

do note: Bower is still a young little birdy, so things are changing rapidly. Authors of Bower components must follow certain conventions and best practices in order for this plug-in to be as accurate as possible. It's not a perfect world out there, so needless to say, some Bower components may not work as well as others.

Getting Started

*If you are new to Grunt, you will find a lot of answers to your questions in their getting started guide.

To install the module:

npm install grunt-bower-install --save-dev

Include the task in your Gruntfile:

grunt.loadNpmTasks('grunt-bower-install');

Create a config block within your Gruntfile:

'bower-install': {
  // Point to the html file that should be updated
  // when you run `grunt bower-install`
  html: 'app/index.html',

  // Optional:
  // If your scripts shouldn't contain a certain
  // portion of a url, it can be excluded
  ignorePath: 'app/'
}

Pop this in your HTML file:

<!-- bower -->
<!-- endbower -->

Install a Bower component:

grunt bower-install:jquery

You're in business!

<!-- bower -->
<script src="bower_components/jquery/jquery.js"></script>
<!-- endbower -->

If you want to uninstall a Bower component:

grunt bower-uninstall:jquery

Behind the Scenes

This plug-in decorates the native Bower commands. So, by saying grunt bower-install:jquery, you are really saying:

bower install jquery --save

After the Bower command finishes executing, this plug-in will take a look at all of the components you have, and determine the best order to inject your scripts in to your HTML file.

Putting script tags that aren't managed by grunt-bower-install is not advised, as anything between <!-- bower --> and <!-- endbower --> will be overwritten with each command.

Examples

A simple sample apple: website | github

Contributing

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

License

Copyright (c) 2013 Stephen Sawchuk Licensed under the MIT license.