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

@jarrku/react-tools--scripts

v0.2.3

Published

Build configuration for React Tools projects

Downloads

4

Readme

Moovly Scripts

This package unifies the webpack bundling for frontend projects. It supports:

  • SASS/LESS
  • Polyfilled environment
  • Babel transpiling
  • Dev/build setup.

Custom webpack configs: moovly-scripts (start|build) --config <path/to/webpack/config> This config will be merged with the default configs.

Folder structure

bin

This contains the executable node script. It executes one of the 3 scripts and handles some errors/throws error when theres an unknown script.

config

This folder contains most of the actual config. It provides a paths file utility and loads the environment variables. The actual webpack configs can be found here as well.

scripts

This folder contains the actual node scripts that will be executed on command.

init is currently WIP -> would serve as boilerplate generator.

The other 3 scripts are basically the way to programatically invoke webpack/jest with some error handling included.

template

This folder is also a WIP, the init script would utilise this folder to generate a frontend boilerplate.

What .env can be used?

  • .env: Default.
  • .env.local: Local overrides. This file is loaded for all environments except test.
  • .env.development, .env.test, .env.production: Environment-specific settings.
  • .env.development.local, .env.test.local, .env.production.local: Local overrides of environment-specific settings.

Files on the left have more priority than files on the right:

  • npm start: .env.development.local, .env.development, .env.local, .env
  • npm run build: .env.production.local, .env.production, .env.local, .env
  • npm test: .env.test.local, .env.test, .env (note .env.local is missing)