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

@kennarddh/test-linaria-library

v1.0.9

Published

Testing linaria component library

Downloads

15

Readme

React JS Boilerplate

Guide

Install Dependencies

npm install

Environment Variables

All environment variables for react application must start with APP_ prefix

To change env prefix change add or remove string from envPrefix variable in vite.config.json

Environtment variables can be accesed using env.<name> or import.meta.env.<name>. Prefix must be included.

Declare env types in src/env.d.ts in ImportMetaEnv interface

The environment variables can be found and modified in the .env file. They come with these default values:

# Port number (optional, default: 3000)
PORT=3000

# Open browser on start (optional, default: true) if value is other than "true" it will be read as false
OPEN_BROWSER=true

Available Scripts

In the project directory, you can run:

Start

Start development build

npm start

Build

build for production.

npm run build

Preview

Preview production build

npm run preview

Clean

Removes all the files generated by the build process.

npm run clean

Lint Check

Finds errors in your code.

npm run lint:check

Lint Fix

Fixes linting errors.

npm run lint:fix

Prettier fix

Fix the code formatting.

npm run prettier:fix

Prettier check

Check the code formatting.

npm run prettier:check

Test

Run all tests

npm run test

Watch test

Watch changed test

npm run test:watch

Watch all test

Watch all test

npm run test:watch:all

Test coverage

Run test coverage

npm run test:coverage

Test changed

Run tests related to changed files based on git (uncommitted files)

npm run test:changed

Note

  • Babel is only for jest to transpile typescript code. If you don't want to use babel you can use vitest
  • tsconfig.json is for react app typescript configuration
  • tsconfig.node.json is for vite and other development tools typescript configuration that will not be included in build result
  • If you want to disable pre-commit or pre-push git hook you can remove the hook inside .husky directory
  • If you want to disable dependabot you need to remove .github/dependabot.yml
  • If you want to disable codeql analysis you need to remove .github/workflows/codeql-analysis.yml