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-fuel

v5.1.0

Published

Atomic Jolt's front-end library code

Downloads

662

Readme

🔋 Atomic Fuel

This package contains all of the front-end library code for Atomic Jolt apps. It includes all front-end code that was previously in the client/libs directory.

🧱 Installation

You should install atomic fuel into each individual app not in the client directory. Just add as a regular dependency.

yarn add atomic-fuel

🧑‍🔬 Usage

All of the code is found in the libs folder which has the following structure

libs/
-- actions
-- api
-- communications
-- components
-- constants
-- decorators
-- graphql
-- libs
-- loaders
-- middleware
-- reducers
-- specs_support
-- store

If you wanted to use, for example, libs/store/configure_store.js you would write the following:

import configureStore from 'atomic-fuel/libs/configure_store.js';

Alternatively, there is an index file which simply exports everything for convenience, so you can do this:

import { configureStore } from 'atomic-fuel';

🛠️ Development

Develop using Storybook, which features hot-reloading, component browsing, and testing of React Components.

Run Storybook: yarn storybook

📝 Note

Component file structure should be organized in the following structure.

src/components/
-- ComponentName/
---- index.js
---- index.spec.js
---- index.stories.js
---- styles.scss

🚧 Building

To build the lib folders and types run: yarn build

🧪 Testing

Run tests: yarn test

Run tests with Chrome DevTools (i.e. use debugger in your tests):

  1. Open a Chromium browser at chrome://inspect
  2. Click on the "Open dedicated DevTools for Node"

Then you can run tests using: yarn test:debug