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

@researchsquarecompany/delivery-scripts

v1.3.7

Published

Kinda like `react-scripts` and inspired by `paypal-scripts`

Downloads

6

Readme

delivery-scripts

A build toolkit built and maintained by the Delivery engineering team. This is kinda like react-scripts and inspired by paypal-scripts.

Why?

We maintain several different applications that have custom build tooling. Managing all of those dependencies in each project was getting out of hand and we found ourselves frequently copy/pasting config between the projects.

Principles

  • Hide internals and expose an easy API that can evolve over the years
  • Developer experience above everything else (including performance if it comes down to that)
  • Easy to upgrade
  • Remove bloated dependency trees in client code

Installation

  yarn add @researchsquarecompany/delivery-scripts

Usage/Examples

Add a ds.config.js to the root of your application

module.exports = {
    outputPath: "dist/",
    manifestPath: "dist/",
    entry: {
        index: "./src/index.js",
    },
};

Documentation

outputPath

This is the folder where the built and bundled assets will end up.

manifestPath

This is the folder where a manifest file will be generated upon successfull build.

entry

An object of key values where the key will generate the name of the bundled file and the value is the location of the file you want to bundle.