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

@cloudsigma/cs-partner-matrixorigin

v1.1.0

Published

### Dependencies

Downloads

205

Readme

Initiate

Dependencies

Install dependencies

npm i

Build/Watch

Opens browser tab containing CloudSigma layout and custom component

npm run serve

Component will open at http://local.cloudsigma.com:3000, if you can not access it add this line to your hosts files.

127.0.0.1 local.cloudsigma.com

Checks

Tests

For tests Playwright is used. You can find tests in tests/e2e folder, to run tests manually execute the following command:

npm test

Package

Checks if package can be build

npm run build

CSS

Styling components can be made only with using inline CSS. For example:

function ComponentWithInlineCss() {
  return (
    <div
      style={{
        width: '10px',
        height: '10px',
        backgroundColor: '#000',
      }}
    >
      Inline CSS
    </div>
  );
}

By following these guidelines, you maintain a clean and isolated styling approach within your components,preventing unintended style conflicts when using external css.

Image Integration

In your component file, use the import statement to bring in the image:

import logo from '../../assets/logo.svg';

Place the imported image in your component's JSX:

 <img src={logo} alt="Logo" />

Organize your images within the project structure. For example:

project-root/
|-- src/
|   |-- component/
|       |-- assets/
|           |-- logo.svg
|-- ...

Icons

For Icons we use Font Awesome version 4.7, you can find icons it provides here

Localisation

You can add custom translations in src/component/locales - [language].js files.

To add translation to component, useTranslation must be imported from react-i18next. For example:

import { useTranslation } from 'react-i18next';

...

function ComponentWithTranslation() {
  const {t} = useTranslation();

  return (
    <h2>
      {t('Translation Key')}
    </h2>
  );
}

You can test different locales by chaning lng: 'en' key in static src/config.jsx file to match desired locale.

i18next Documentation