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

react-vite-component-template

v0.0.0

Published

Template for building a **React component library**, with **Vite**, **TypeScript** and **Storybook**.

Downloads

19

Readme

react-vite-component-template

Template for building a React component library, with Vite, TypeScript and Storybook.

📐 Linting & formatting

Stylelint, Eslint & Prettier configured.

🧪 Testing

Using Vitest with jsdom environment and ready for generating coverages.

🤖 Scripts

| Script | Function | | :---------------: | ---------------------------------------------------------------------------------- | | build | Build the dist, with types declarations, after checking types with TypeScript. | | storybook | Start a Storybook development server. | | build-storybook | Build the Storybook dist. | | test | Run the tests with Vitest using jsdom and starts a Vitest UI dev server. | | coverage | Generate a coverage report, with v8. | | lint | Lint the project with Eslint. | | lint:fix | Lint and fix the project with Eslint. | | format | Check the project format with Prettier. | | format:fix | Format the project code with Prettier. | | stylelint | Lint the styles code with Stylelint. | | stylelint:fix | Lint and fix the styles code with Stylelint. |

🏛️ Exposing library entry points

Remember to align fileName value in lib object within vite.config.ts...

export default defineConfig({
  // Rest of vite.config.ts
  build: {
    lib: {
      entry: resolve(__dirname, 'src/main.ts'),
      name: 'MyLib',
      fileName: 'my-lib',
    },
  },
  // ...
})

With import and require values in exports, in package.json

{
  // Rest of package.json
  exports: {
    '.': {
      import: './dist/my-lib.js',
      require: './dist/my-lib.umd.cjs',
    },
  },
}

🌐 Exposing types entry point

If you modify the structure or naming, update they types key in package.json.

{
  // Rest of package.json
  types: './dist/main.d.ts',
}