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

@terminal-packages/fe-theme

v2.1.0

Published

![Test Action Status](https://github.com/Terminal-Systems/fe-utils/workflows/Tests/badge.svg) ![Publish Action Status](https://github.com/Terminal-Systems/fe-utils/workflows/Publish/badge.svg?branch=master)

Downloads

17

Readme

Test Action Status Publish Action Status

FE Base Package

Base Typescript boilerplate to build FE packages on top of it

Available commands

  • build: build src directory
  • build:cjs: build src directory using cjs modules
  • build:esm: build src directory using esm modules
  • storybook: run storybook on port 9001
  • clean: delete core folder
  • lint: run eslint on src folder
  • lint:fix: run eslint in fixing mode on src folder
  • test: run tests

Note that our build directory is called core, that way you can publish the package and using it package-name/core/SomeComponent like material-ui

Get started

  1. Clone the repo: git clone https://github.com/Terminal-Systems/fe-base-pkg.git <package-name>
  2. Go to the project folder and edit the package.json:
    • name: package name (use @org-name/pkg-name for orgs)
    • version: 1.0.0
    • author: list of authors
    • repository.url: git+https://github.com/<username>/<package-name>.git
    • bugs.url: https://github.com/<username>/<package-name>/issues
    • homepage: https://github.com/<username>/<package-name>#readme
  3. Change the git remote url (you must to create an empty github project first):
    git remote rm origin
    git remote add origin <your-new-git-remote-url>

Download last base library updates

As a result of changed the remote url for the library you will not be able to fetch the last updates using git pull origin, instead, you should use:

git remote add fe-base-pkg https://github.com/Terminal-Systems/fe-base-pkg.git
git checkout -b <some-temp-branch-name>/upgrade
git fetch fe-base-pkg
git merge fe-base-pkg/master

Build a non React based library

If you want to create a non React based library, you should remove some dependencies that are not required. To do that, please remove the following libraries from package.json devDependencies and peerDependencies:

  • @material-ui/core
  • prop-types
  • react
  • react-dom
  • @types/prop-types
  • @types/react
  • @types/react-dom

peerDependencies

If you need to use a package that should be provided by your host app, please adding it as a peerDependencie to avoid library duplications on node_modules.

Important Note: peerDependencies are not installed by npm install or yarn install. So in order to install peerDependencies on dev enviroment you can add your required package as a peerDependencies and devDependencies. Otherwise, you can use a package like install-peers-cli

More Info Here

Workflow

Our library workflow is pretty straightforward: use develop branch to add any new feature and master to publish on npmjs.com

Testing

This boilerplate is pre-configured with jest. You can run your tets with the command: npm test. If you need to use some of the enzyme render methods, please consider use the test-utils provided by @material-ui/core/test-utils:

  • createMount
  • createShallow
  • createRender

More Info Here

Notes

Before commit any change, husky is going to run eslint in fixing mode, run tests and try to build the project to avoid pushing commits that break something

Utils