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

gulp-ng-test-utils

v0.0.5

Published

ng-test-utils for gulp

Downloads

18

Readme

gulp-ng-test-utils

This project has changed it's name to gulp-tang. All further updates will be under the new name. Change your dependencies now!

Gulp is a great build system, but most users will benefit more by using the karma-preprocessor to apply the transforms for their tests. If you are not using karma, or have a need to package up your tests with the transforms applied, then read on.

Install:

npm install --save-dev ng-test-utils gulp-ng-test-utils

Since this is all about testing, you almost certainly want to enable source-maps. There are two ways to accomplish this.

Using gulp-sourcemaps is the recommended way if you are chaining this transform together with others that support gulp-sourcemaps.

var gulp = require('gulp');
var ngTestUtils = require('gulp-ng-test-utils');
var sourcemaps = require('gulp-sourcemaps');

gulp.task('instrument-test-files', function (){
  return gulp.src('tests/*.js')
    .pipe(sourcemaps.init())
    .pipe(ngTestUtils())
    .pipe(sourcemaps.write())
    .pipe(gulp.dest('build/tests'))
});

Using ng-test-utils internal source map support is handy if it is the only transform being applied to your test code, or if up/downstream transforms do not support gulp-sourcemaps.

gulp.task('instrument-test-files', function() {
  return gulp.src('tests/*.js')
    .pipe(plugin({
      sourceMap:true
    }))
    .pipe(gulp.dest('build/tests'))
});

Check out the examples and gulpfile.js folder on github for more ideas.