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

@simmalugnt-se/next-components

v1.3.1

Published

React and Next components created by Simma Lugnt

Downloads

1

Readme

Next components library

By Simma Lugnt

Info

This project was setup using inspiration from these articles:

Using this library

1. Install into your project

cd path/to/my-project
npm i @simmalugnt-se/next-components

2. Import the components you like

// Page.jsx

import { Hero, Button } from "next-components"

const Page = () => {
  return (
    <Hero title="Do you like buttons?">
      <Button label="I do!" />
      <Button label="I don't..." />
    </Hero>
  )
}

Creating components

1. Create a new branch

Create a new branch for your work. Examples:

  • feature/slider-component
  • fix/slider-max-width

Create a PR for your branch and describe the purpose.
Examples:

Add a slider component that shows images with text

or

Set a max width for slider to avoid it extending the window width

2. Add your component

Add a file under src/lib. Example:

src/lib/components/MyComponent.tsx

Export the component in src/index.ts:

import Button from "./lib/components/Button";
import Hero from "./lib/components/Hero";
+ import MyComponent from "./lib/components/MyComponent";

- export { Button, Hero };
+ export { Button, Hero, MyComponent };

2. Develop according to guidelines

You must follow the guidelines

3. Testing your component

  1. Build this project:
    npm run build
  2. Import locally in a test project
    cd path/to/test-project   
    npm install ../path/to/next-components
  3. Import and use your component to make sure it works as intended!
    import { MyComponent } from 'next-components'
    // ...
    <MyComponent someProp='Test content' />

3. Write an automated test

@TODO: Add a guide for tests here

3. Update and publish this package

  1. Build the project
    npm run build
  2. Bump the version
    @TODO: Add info here
  3. Publish the package
    npm publish

Guidelines for developing components

These are very important in order to keep the components library usable and maintainable.

1. Plan

  • Identify the use cases for your component and decide which properties and features it really needs
  • Check with a co-worker to test your idea before proceeding

2. Write

  • Avoid complexity - write clean and readable code
  • Comment your code where needed
  • Avoid ESLint errors and warnings (or else your code won't build)

3. Test

  • Test your code with different options and props
  • Let someone else review your code