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 🙏

© 2025 – Pkg Stats / Ryan Hefner

react-get-started

v1.0.14

Published

A basic setup of React development environment

Downloads

22

Readme

Basic setup of a React project

This is NOT a npm package intended for installation. So do NOT install it.

This is a basic setup of React with Babel, Webpack with minimum dependencies to get you started.

Get started

npx react-get-started my-app

Tips

If you don't like the browser auto-reloads every time you change the code, then add inline: false to devServer property in webpack.dev.js.

...
devServer: {
    compress: true,
    port: 5000,
    overlay: true,
    inline: false
}
...

Hot reload in Windows 10 WSL2

Refer to https://stackoverflow.com/questions/62780245

Develop with Sass

npm i --save-dev sass sass-loader

In webpack.dev.js, add settings of plugins in rules.

rules: [
    ...,
    
    {
        test: /\.s[ac]ss$/i,
        use: [ 
            'style-loader',
            'css-loader',
            'sass-loader'
        ]
    }
]

Then, you can add paths of Sass files in your source code, e.g.

import React from 'react';
import './index.scss';

Add TypeScript

npm i --save-dev @babel/preset-typescript @types/node @types/react @types/react-dom ts-loader typescript

Update Webpack config

Add TypeScript loader

rules: [
    ...,
    
    {
        test: /\.tsx?$/,
        exclude: /node_modules/,
        use: 'ts-loader'
    },
    ...
]

Resolve file extensions

Add extensions with ts, tsx so when import TypeScript modules, you don't have to type .ts or .tsx.

resolve: {
    extensions: [".js", ".json", ".ts", ".tsx"],
},
modules: { 
    ... 
},

Quoted from Webpack official site

Using this will override the default array, meaning that webpack will no longer try to resolve modules using the default extensions.

Update entry with a tsx file, for example

entry: './src/index.tsx',
output: { 
    ... 
},    

Update .babelrc

{
  "presets": [
        ...,
        "@babel/preset-typescript"
    ]
}

Add tsconfig.json

Here is an example. Some adjustments may be required as per project's needs.

{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "react",
    "outDir": "./built"
  },
  "include": [
    "src"
  ]
}