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

atomic-reactor

v3.2.3

Published

Atomic Jolt's React build tool

Downloads

31

Readme

Atomic Reactor

This package contains all of the development and production build code and should be treated as the core of the front-end applications.

Installation

This package should be installed into the client node_modules folder as a dev-dependency.

yarn add --dev atomic-reactor

This gives you access to all of build processes that were previously in the client folder. You will need to reference the from the node_modules in any scripts that used the build process. For example (in root package.json)

{
  "scripts": {
    "hot": "./client/webpack.hot.js"
  }
}

becomes

{
  "scripts": {
    "hot": "atomic-webpack-hot --configDir=client/config"
  }
}

Atomic Reactor Modes

Atomic Reactor supports multiple Javascript applications along with a templating engine that can built your html and assets.

  1. Running multiple servers - one per application. Just run yarn hot and each application will be served independently on it's own port starting with the 'hotPort'

  2. Running a single app at a time. Run yarn hot --app [application name] and only a single application will be started.

  3. Only outputting Javascript and assets while ignoring all html. Running yarn hot --onlyPack will ignore all html files and start a server that will output assets. This is useful when used in conjunction with another application framework like Ruby on Rails.

  4. Outputting a single site that contains html to support the other applications. Build your html in one application and the in all other applications set options.json to: { "rootOutput": true, "onlyPack": true }