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

automagical

v1.0.3

Published

(alpha build) Making Webpack as easy as Nodemon

Downloads

11

Readme

Automagical

The one-click experience for JavaScript development

Browser HMR (hot module reloading), static file server and node reloading all-in-one.

[GIF showing starting a project][datauri://]

  • Special thanks to Webpack, Nodemon, Webpack-Dev-Server projects

Quick start

npm install automagical -g

Create a barebones, new project (or if you like you're existing project you can keep your existing project).

auto new react

Start a HMR server in your working directory

auto

New Project (coming soon)

Create a new react project. This will create an up , will add mobile icons as wellto date scaffold that can fully run by itself. , any inline comments that are a file path will get and replace the comment with the file

auto react

Install other packages when the package starts.

auto react --install redux

By default automagical will upgrade every library to the highest version number (betas are opt-in only). If something doesn't work reinstall with the --safe flag to use the specific library version in the original package.json.

auto react --safe

Development

Start the hot reload server.

auto start # or npm run watch

Options for hot reloading development server.

auto start \ # by default, separate files by routes for insanely fast loading
  --port 1234 \ # default port is 8080. use this to override the port
  --proxy \ # url to proxy calls to
  --https \ # use a https server to get access to all browser APIs
  --offline \ # include service worker to test/validate offline support, will add mobile icons as well
  --polyfills \ # array of URLs for polyfills to preload
  --html my-index.html \ # use an alternate index.html to server the app, any inline comments that are a file path will get and replace the comment with the file

To start development you'll want to bring up a server. The automagical server will use webpack to hot swap modules to give instant reloads. Packages will be auto-installed in your project folder.

Deploy

How to deploy.

auto build \ # by default, separate files by routes for insanely fast loading
  --offline \ # add a service worker to the index.html
  --embed \ # package html, css, js, imgs, fonts all into a single .js file (great for CMS deployments)
  --node \ # package run server side in node
  --lib \ # separate files by components and exclude react and other high-level dependencies
  --html my-index.html \ # use an alternate index.html to server the app