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-script-install

v0.1.3

Published

Simple plugin for injecting script tags to your html file.

Downloads

1

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

patrykziempatrykziem

Keywords

gruntplugin

Readme

grunt-script-install

Simple plugin for injecting script tags to your html file.

Getting Started

This plugin requires Grunt ~0.4.2

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-script-install --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

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

For dependecies to be injected pop this snippet into your html:

<!-- script-install -->
<!-- end-script-install -->

The "scriptInstall" task

Overview

In your project's Gruntfile, add a section named scriptInstall to the data object passed into grunt.initConfig().

grunt.initConfig({
  scriptInstall: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.html

Type: String Default value: 'index.html'

A path to html file where script tags will be injected.

Usage Examples

This is an simple example that will pick up all js files specified and inject them in index.html file.

Assuming this is a project structure:

\app
	\scripts
		\moduleA
			fileA1.js
			fileA2.js
		\moduleB
			fileB1.js
		\coffee
			fileCoffee.coffee
		file1.js
	index.html

Html file:

<!DOCTYPE html>
<html>
<head>
	<title></title>
</head>
<body>

	<!-- script-install -->
	<!-- end-script-install -->

</body>
</html>

Grunt config:

grunt.initConfig({
  scriptInstall: {
    dev: {
	    options: {
	      html: 'index.html'
	    },
	    files: [
	      {
	        expand: true,
	        cwd: 'app',
	        src: [
	          'scripts/*',
	          'scripts/moduleA/**/*',
	          'scripts/moduleB/**/*',
	          'scripts/coffee/**/*'
	        ],
	        ext: '.js',
	        filter: 'isFile'
	      }
	    ],
    }
  },
});

This will generate following html:

<!DOCTYPE html>
<html>
<head>
	<title></title>
</head>
<body>

	<!-- script-install -->
	<script src="scripts/file1.js"></script>
	<script src="scripts/moduleA/fileA1.js"></script>
	<script src="scripts/moduleA/fileA2.js"></script>
	<script src="scripts/moduleB/fileB1.js"></script>
	<script src="scripts/coffee/fileCoffee.js"></script>
	<!-- end-script-install -->

</body>
</html>

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.