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

atomico-base

v0.0.1

Published

a repo to start with atomico

Downloads

3

Readme

AtomicoAtomico

Hi, I'm @uppercod, creator of Atomico and I want to thank you for starting with Atomico.

If you need help you can find it at:

twitter discord documentation discord

Now what you have installed is a quick start kit based on Vite, which you can scale for your project, now to continue you must execute the following commands:

  1. npm install
  2. npm start : Initialize the development server
  3. npm build : Optional, Generate a build of your project from the html file index.html.

Workspace

Recommended structure

src
  |- my-component
  |  |- my-component.{js,jsx,ts,tsx}
  |  |- my-component.test.js
  |  |- README.md
  |- components.js # import all components

The npm run create command, will create a webcomponent with the recommended structure, the template of this webcomponent can be edited in templates/component.md.

Scripts

npm run create

Create a new webcomponent inside src, according to the recommended structure, the template of this webcomponent can be edited in templates/component.md.

npm run start

initialize Vite server

npm run build

package the app using de Vite

npm run test

Run a test environment in watch mode, as configured in vite.config.js.

npm run coverage

Run a test environment with coverage, as configured in vite.config.js.

npm run exports

Allows you to export your project to npm, this command executes changes in package.json before exporting and the changes will be reverted once exported.

temporary changes are:

  1. generation of the packages.json#exports
  2. generation of the pages.json#typesVersions
  3. Compilation of the files and generation of the types if the --types flag is used.

frequent questions

How to add postcss?

@atomico/vite, allows to preprocess the css template string through postcss, to use this feature add in vite.config.js the following options:

import atomico from "@atomico/vite";
import { defineConfig } from "vite";

export default defineConfig({
  ...
  plugins: [
    atomico({
      cssLiterals: { postcss: true }, // 👈 CONFIGURATION TO ADD
    }),
  ],
});

To use postcss at least 1 plugin is required.

"postcss": {
  "plugins": {
    "postcss-import": {}
  }
}

How to publish on github page?

Add to package.json#scripts.build:

--outDir docs # modify the destination directory
--base my-repo # github page folder