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

ad-builder

v0.0.0-beta.1

Published

This is a framework that allows you to build ad quickly and efficiently.

Downloads

6

Readme

🧱 Building Blocks

Here's an explanation of all of the scripts in package.json.

  • lint - This a quick linting commmand that should help you make sure that when you do a pull request that all of the code that you've added is lint compliant.
npm run lint

  • tsc:build - This is a helper function that you should not use. All it does is convert the TypeScript files into JavaScript files.
npm run tsc:build

  • webpack:dev - This is a helper function that you should not use. All it does is uses the webpack config to create one script.
npm run webpack:dev

  • webpack:prod - This is a helper function that you should not use. All it does is uses the webpack config to minify and create one script with a source map.
npm run webpack:prod

  • build:dev - This is the script you should use to develop the framework. The test file is located in public. If you notice this build script uses another config. This config is used just for hot loading the files. (This is not working at the moment.)
npm run build:dev

  • build:prod - This is a script you should use when you want to release this framework into the wild.
npm run build:prod

🧑🏽‍💻 Development Procedure

So this has a bit of a weird development structure. I'm still working on the scripts and the procedure, but this works for now.

Run the build command for development.

npm run build:dev

Then run the unused commmand in the package.

npm run unused

When you update anything in the public folder, all you have to do is refresh the page. However if you update something in the src folder then you will have to stop the current process in the terminal. (^c)

Then you will have to run the build:dev command. Then right after you can run the unused command. This will get you testing out the framework.

There's a couple things to note:

  • Because the build:dev command has rm -r ./dist in it, if you don't have a dist folder then you will have to make a dist folder so that it can have something to delete.
  • In ./public/index/html you'll see this:
        <div id="items" style="display: none;">
            <img id="title" src="./walk/title.jpg" />
            <img id="dvd" src="./walk/dvd.png" />
            <img id="clouds" src="./walk/clouds.jpg" />
        </div>

This is here because when using webpack to watch the public folder it renames all of the files or removes them from their folders. Also if you don't declare all of the files you're using in the localhoast then those files will not be available.