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

@kaliber/react-bundle

v0.0.2

Published

A test for bundling dependencies and scaffolding in a module

Downloads

6

Readme

Kaliber React Bundle

!! Warning This package is currently for internal proof of concept at Kaliber. It needs work and cleaning up before it becomes useful to the public domain.

This project was inspired by create-react-app. We borrow parts that are useful to us but the result will be opionated for use within Kaliber.

Goals

  • Quick to set up new project
  • Bundle common deps in a single dependency for easy version management and updates
  • Include development server with HMR
  • Standardize configuration and common file locations
  • Hide as much complexity as possible while still exposing enough config to make it work across projects
  • Encourage uniform use of technologies across Kaliber React projects

Usage

npm install --save @kaliber/react-bundle

Add the start and build script to your project package.json

"scripts": {
  "start": "react-bundle start",
  "build": "react-bundle build"
}

Requirements

NPM >= 3, which comes with Node >= 5.

The code itself is also compatible with older versions of Node, since internally we use babel-node for running the scripts. But for bundling dependencies in a single module we rely on the behavior of NPM 3 which installs dependencies in a flat structure.

Dev Server Config

The start script launches the dev server. You can pass optional parameter to it to configure the port and proxy settings:

react-scripts start --proxyTarget http://localhost:9000 --proxyMatches 'api,content'

Available options are:

  • --port: The port on which the dev server mounts. Defaults to 8000.
  • --proxyTarget: The target to proxy calls to.
  • --proxyMatches: The routes on which to match the proxy, as a comma seperated list. Defaults to api. Matches are converted to regexp so that api,content becomes [/^\/api\/.*/, /^\/content\/.*/]

Project structure assumptions

In order to make your project compatible with react-bundle the following assumptions are made:

  • app/main.js is the entry point
  • ... to be documented

Todo

  • check out https://github.com/kriasoft/react-app
  • figure out vendor bundle config. package.json?
  • progress display for build
  • use dotenv for config?
  • try eslint config from create-react-app
  • create app/static folder en copy to build output. Replace favicons en content in mobi3 proxy

Cleanup

  • rename target -> build
  • rename app -> src
  • main.js -> index.js?