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

pep-rt-web

v0.0.5

Published

RT's app for web

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

ldipasqualeldipasquale

Keywords

Readme

coverage report

PEP RT WEB

Usage

  1. Requirements

  2. Clone project code.

git clone https://gitlab.com/viemed/pep/pep-rt-web.git pep-rt-web
cd pep-rt-web

  1. Set up Gitlab NPM's registry. To do so, follow the next steps:

    3.1 Create a Personal Access Token on GitLab with read_registry, write_registry and api permissions. 3.2. Set this token as an environment variable named NPM_TOKEN

  2. Installation dependence.

yarn install

  1. Configuring app

    5.1 Environment Variables

    Before starting or building the app, you'll have to create a `.umirc.local.js` file at root to fill up environment variables. There is already created a `.umirc.local.example` file for guidance. However, you'll have to ask the team for some keys for AWS and other services.

    5.2 Lokalise

    Since we are using https://lokalise.com/ for internationalization, you must download the translations for the app. To do so, you must run the following script (replace the placeholders first):

$ lokalise --token xxxxxxxxxxxxx export 765489265cd03586bff563.09788970 --type json --bundle_structure 'messages.json' --unzip_to src/locales/en --placeholder_format icu

  2. Start local server.

yarn start
  1. Run tests
yarn test
  1. After the startup is complete, open a browser and visit http://localhost:7001, If you need to change the startup port, you can configure it in the .env file.

Build

First execute the following command,

npm run build

The build command will package all resources, including JavaScript, CSS, web fonts, images, html, and more. You can find these files in the dist/ directory.

Rollbar

window.onerror("TestRollbarError: testing window.onerror", window.location.href)

and make sure we get the right environment in Rollbar report