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

@cybercomsweden/frontend-ci-scripts

v2.2.0

Published

- [Install package](#install) - [Add proxy to development](#proxy)

Downloads

19

Readme

frontend-ci-scripts

Install

npm install --save-dev @cybercomsweden/frontend-ci-scripts

Usage

There are a few scripts exposed to help you with your development

  • lint / runs eslint on your project
  • format / run prettier on your project
  • test / runs jest on test files in src with *.spec|test.js or in the __test__ folder
  • precommit / runs lint, test and format as a precommit hook
  • start / a webpack-dev-server for quicker react development

Format

"format": "frontend-ci-scripts format"

format runs prettier in the background and formats all your files. You can send args to prettier if you want to format any specific files by adding them to the scripts

"format": "frontend-ci-scripts format src/**/*"

To be noted On unix systems you need to prevent the glob from being prematurly evaluated do this by putting it in ''

"format": "frontend-ci-scripts format 'src/**/*'"

Precommit

During installation git hooks is setup for you. add the following script to your package.json for it to run during each commit

"precommit": "frontend-ci-scripts precommit",

Editor Integration

ESLint integrations: https://eslint.org/docs/user-guide/integrations

Prettier integrations: https://prettier.io/docs/en/editors.html

You can expose our option files to your editor by adding them to your package.json


"eslintConfig": {
    "extends": "./node_modules/frontend-ci-scripts/.eslintrc.js"
  }

or add your own .eslintrc file and extend the path above


For Prettier create a .prettierrc.js and add the following

module.exports = require('frontend-ci-scripts/.prettierrc');

Proxy

In development you sometimes need to proxy request

Do this by adding a proxy key to you package.json

"proxy": "[dependencieName]" || "path/to/proxy",

It expects a js object or json file.

Mocks

If webpack needs to serve mock pages, add a mocks key to package.json.

"mocks": "path/to/mocks",

It expects a path to a directory (should be relative to the project root).

Production Build

Public Path

If an environment variable PUBLIC_PATH is set, the webpack build will use that. Otherwise it defaults to '/'.

Inspiration

create-react-app and kcd-scripts