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

@b08/bucket-generator

v1.0.3

Published

generator to create index.ts files

Downloads

43

Readme

@b08/bucket-generator, seeded from @b08/generator-seed, library type: generator

This generator creates index.ts files.

usage convention

It is recommended to create index file only for your types and interfaces, never for the code.
For example, I use following naming convention for code.
user.type.ts - file containing types like "interface User {...}", which describes BL level entity.
user.model.ts - file containing types like "interface UserModel {...}", which describes REST API level entity.
user.service.ts - file containing classes like "class UserService".
...and so on
And then I generate buckets only for following file types: type, model, const, enum

usage

import { generateBuckets } from "@b08/bucket-generator";
import { transformRange, transform } from "@b08/gulp-transform";
import * as changed from "gulp-changed";

const options = { lineFeed: "\n", quotes: "\"" };

export function buckets(): NodeJS.ReadWriteStream { // this is a gulp task
  const types = ["type", "model", "const", "enum"];
  const files = types.map(type => `${settings.appPath}/**/*.${type}.ts`);
  return gulp.src(files)
    .pipe(transformRange(files => generateBuckets(files, options)))
    .pipe(changed(dest, { hasChanged: changed.compareContents }))
    .pipe(logWrittenFilesToConsole)
    .pipe(gulp.dest(settings.appPath));
}

const logWrittenFilesToConsole = transform(file => {
  console.log(`Writing ${file.folder}/${file.name}${file.extension}`);
  return file;
});

@b08/gulp-transform is a gulp plugin designed to work with generators. \