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

gun-pack

v1.0.14

Published

react build tools

Downloads

6

Readme

gun-pack

react cli   react compiler

github

usage

react build tool, Support Typescript

    yarn add gun-pack 
  • package.json scripts
   gun-pack  dev
   gun-pack  build

   // after you build, also you can startup service
   gun-pack  server

You can customize your compiler configuration in your root directory

  • gun.config.js example:
const config = {
    port: 9000,                         
    defaultEntry: true,
    defaultHtmlPlugin: true,
    openBrowser: false,
    writeToDisk: false
    publicPath: '/',
    entry:null,                      // Object<webpackEntry> | null | array<webpackEntry>
    proxy: {
       '/api': {
           target: 'http://localhost:3000',
           pathRewrite: {'^/api': ''},
       },
    },
    htmlPluginOption: [                    //  null | Array<object>
        {                   
            template: path.join(__dirname, './src/index.html'),
            chunks: ['main', 'react'],
            options
        }
    ], 
    definePluginOption:{
        'process.env.NODE_ENV': JSON.stringify('production'),
        'definePlugin':JSON.stringify('definePlugin'),
    },
    hot: true,
    liveReload: false
}

module.exports = config

Parameter description

| parameter | description | | ---- | ---- | | port | listener port ; default 9000 | | open_browser | auto browser open page | | default_entry | Use default entry /src/index.js ; default true | | default_htmlPlugin | Use default htmlPlugin /src/index.html ; default true | | writeToDisk | default false | | publicPath | default '/' | | entry | Object<webpackEntry> / null when defaultEntry is false, customize yourself | | proxy | Object<webpackDevServerProxy>| | htmlPluginOption | Array / null when defaultHtmlPlugin is false, customize yourself | | definePluginOption | Object<webpack.definePlugin.option>, when gun-pack dev , process.env.NODE_ENV default development, when gun-pack build , process.env.NODE_ENV default production|