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

charge-hour-modal

v1.0.1

Published

This template is designed to accelerate the start of new npm package or custom MicroFrontend package.

Downloads

5

Readme

New Frontend boilerplate

This template is designed to accelerate the start of new npm package or custom MicroFrontend package.

To start using it you have to clone or fork this repo make an fresh install of packages and run the npm start command.

Npm Commands

# to initialize the dev server in local development
npm run start

# Prepare husky git hooks
npm run prepare

# to make a production ready build of the project
npm run build

# to execute the testing process on test files
npm run test

Default Config

The project is serve using a Webpack Dev Server and have a Webpack configuration with the following settings:

  • JS, TS, TSX, CSS and SVG loaders
  • Dotenv webpack plugin to include .env variables
  • TerserPlugin webpack plugin to minify files
  • Module Federation webpack plugin (not enabled by default)
  • BundleAnalyzerPlugin (not enabled by default)

Module Federation Config

To enable Module Federation you have to go to the Webpack Config File and uncomment these lines

new ModuleFederationPlugin({
      name: "MicroFrontTemplate",
      remoteType: "var",
      filename: "templateEntry.js",
      exposes: {
        "./ExposedComponentKey":
          "./exposedComponentPath",
      },
      shared:[]

After that you have de decide which components you want to expose an add them into the config, the same thing apply with the shared deps.

To know more about Module Federation config please visit: https://webpack.js.org/concepts/module-federation/