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

@plurix/ecom-components

v1.4.0-commerce.0

Published

## Dependencies

Downloads

1,114

Readme

@plurix/ecom-components

Dependencies

Use yarn to install all dependencies and prepare husky (used to run scripts in git steps).

Folder Structure

  • lib: files that will be compiled and published in the @plurix/ecom-components package
  • src: local development

How to Create a New Component in the Package

  • Create a new folder in lib/packages, with your component name. Example: MyComponent;
  • Create a .tsx file inside this new folder and export a component from there. Example:
// lib/packages/MyComponent/MyComponent.tsx

export const MyComponent = () => {
  return <h1>My Component</h1>
}
  • Export the new component in lib/main.ts. Example:
// lib/main.ts

export { MyComponent } from './packages/MyComponent/MyComponent'
  • Create a new file called <component-name>Example.tsx in src/examples and import your component. Example:
// src/examples/MyComponentExample.tsx

import { MyComponent } from '../../lib/main'

export const MyComponentExample = () => {
  return (
    <div className="my-component-example-container">
      <MyComponent />
    </div>
  )
}
  • Export the new example component in src/index.ts. Example:
// src/examples/index.ts

export { MyComponentExample } from './MyComponentExample'
  • Run yarn dev;
  • Open the localhost link in the terminal;
  • Choose your component in the sidebar. Now, you can develop your component and test it with fast refresh.

OBS: If you need to use css in your components, create them as <component-name>.global.css and import them in your Lib Component. Then, you are able to use that in VTEX IO and VTEX Faststore.

Imgur

Publishing

  • After finishing your component changes, upgrade the package version in package.json and create an entry in CHANGELOG.md.
  • Commit and push your changes to the remote repository. It will run the husky scripts: commitlint, prettier, lint, tests, and build.
  • After all scripts pass successfully, run npm publish in your terminal.
  • Copy the published version from your terminal and install it in another repository.
  • You can import the new component by using:
import { MyComponent } from '@plurix/ecom-components'
import '@plurix/ecom-components/dist/styles/my-component.global.css' // If you are using css