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

location-microfrontend

v0.1.0

Published

Starter kit for React, Webpack (with Hot Module Replacement), Typescript and Babel.

Downloads

2

Readme

Location Micro Component

Tech Stack Required

  • React 18
  • Node 18.16+
  • PNPM (to install dependencies)
  • RSPACK (for build configuration)

Force install packages using pnpm only

We have applied force install using pnpm package only (NPM/YARN or any other package manager won't work) To apply force install we have incleded below script to package.json

  "engines": {
    "npm": "Use PNPM package manager to install Dependencies/devDependencies",
    "pnpm": ">= 8.6.5",
    "node": ">= 18.16.0"
  }

Then created .npmrc file and included below command

engine-strict = true

Create credentials file inside <project-root>/package/view directory

Folder will contain index.ts file which will include your token and user details in below format.

export const config = {
  isRTMRequired: true,
  params: {
    merchantId: <MERCHANT_ID>,
    brandId: <BRAND_ID>,
  },
  environment: <ENVIRONMENT [STAGHE/LIVE/PRE-ALPHA]>,
  token: <ACCESS-TOKEN-WITHOUT-BEARER>
};

Environment Variable

We need to create .env file in root direectory <project-root>/, include below environment variable to run the project.

NODE_ENV=development
RSPACK_CONFIG_VALIDATE=loose rspack build
REACT_APP_MODE=development
GITHUB_REF_NAME=main
SENTRY_AUTH_TOKEN=<SENTRY_AUTH_TOKEN>
SONAR_AUTH_TOKEN=<SONAR_AUTH_TOKEN>
RTM_API_KEY_DEV=<RTM_DEV_KEY>
RTM_API_KEY_PROD=<RTM_PROD_KEY>
GOOGLE_MAP_KEY=<GOOGLE_API_KEY>

Enable loose validation mode will print out erroneous configurations but will not throw error.

RSPACK_CONFIG_VALIDATE=loose rspack build

Enable loose validation mode, without printing errors or throwing error.

RSPACK_CONFIG_VALIDATE=loose-silent rspack build

To run sonarqube validation checks include below environment variable, you will get the token from

https://sonar.anywhere.co/ SONAR=

To capture sentry log include below environment variable

https://sonar.anywhere.co/ SENTRY_AUTH_TOKEN=

Debug development environment

DEBUG=builder pnpm dev

Start Project Command

npm run start:view