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

cra-template-microfrontend

v1.1.1

Published

CRA Default + Microfrontend templates.

Downloads

2

Readme

Create React App Microfrontend

Project short description

Table of Contents

Config

After create-react app, you need to configure your package.json to define project scope. To do this, change the name on scope in package.json. To grant render cache techniques, check all scopes in all projects.

This name must be equal for all microfrontends under the same orchestrator

{
  "scope": "mfscope" // micro-frontend-scope
}

Development

To start development server, run:

yarn start

If you need to check css dev errors, run in two different terminals:

# on first terminal
yarn css
# on second terminal
yarn react

Hard to find bugs? Try this debugging methods:

  • VsCode
  • Manual debugging: add debugger on your code and open browser Dev Tools

Deploy

Just run this command:

yarn build #apply GENERATE_SOURCEMAP=false INLINE_RUNTIME_CHUNK=false to react-scripts

Scripts

All available scripts

yarn css

Start postcss in watch mode to observe all mutation on src/styles/css/index.css file or nested imports. Generate a new stylesheet in src/styles/css/dist.css.

yarn css:prod

Build all css to production mode, using postcss and flag NODE_ENV=production.

yarn react

Starts react development server with fast refresh.

yarn start

Apply yarn css and runs yarn react with concurrently.

yarn build

Compile CSS and JS in production mode, using a custom webpack config to work with render. This script doesn't generate SOURCE_MAP files and inline javascripts.

yarn build:source-map

Build only Javascript and current CSS stylesheet, but generate sourcemaps to analyze bundle size.

Troubleshooting

My bundle size is too big. Help Me!!!:

First, this project already use code splitting by default. Check your imports on src/routes/index.tsx and remember, all components loaded by React.lazy must be export as default. If your bundle size is still large even with code splitting, try using analyze to identify large libraries in your project.

yarn build:source-map
yarn analyze

I don't like fast refresh, how to disable?

Assign FAST_REFRESH=false before run start or react: FAST_REFRESH=false yarn start