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

@marknotton/source-exists

v1.1.0

Published

Report files that don't exist from an array of relative paths.

Downloads

1

Readme

Source Exists

Made For NPM

Report files that don't exist from an array of relative paths.

Installation

npm i @marknotton/source-exists --save-dev
const sourceExists = require('@marknotton/source-exists')

Usage

Simply pass in the same array of source files into the sourceExists function to check if the files exist.

Special cases where ignored files (!) or globs (*) are used will not be checked. Only full file paths relative to where the Gulp task file is located.

gulp.task('scripts', () => {

  let files = [
    "modules/scripts/file.js",
    "public/assets/js/galleryzzzz.js",
    "public/assets/js/inits.js",
    "public/assets/js/*/**.js"
  ]

  sourceExists(files)

  return gulp.src(files)
  .pipe(gulp.dest("combined.js"))
});

This will output something like this in your CLI:

[12:32:01] Missing: public/assets/js/galleryzzzz.js Could not find this file

You can pass in a second parameter too. A true boolean will cause your task to throw an error if a source file couldn't be found rather than outputting a CLI message. Alternatively you can set your own callback function to do what you like. The callback function passes back an array of strings.

sourceExists(files, message => { console.log(message); })