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

appirio-tech-react-components-test10

v0.0.1

Published

Topcoder UI Kit library of components for our React apps.

Downloads

3

Readme

npm version Build Status

React Components

This repository is used to distribute reusable React components.

Installation

We use node 8.x and npm 6.x, so you may need to download a new version of node. The easiest way is to download nvm. We have a .nvmrc file in the root of the project, so you can just run nvm use to switch to the correct version of node.

Install dependencies by running the following in the root of the project:

  • npm i
  • Note: You must use npm 6. Type npm -v to ensure you have a 6.x version.

NPM Commands

  • To run locally, run npm run dev and head to localhost:8080
  • To run the test runner: npm test
  • To make sure your code passes linting: npm run lint
  • To create the build: npm run build

Contributing

Pull Requests

To contribute to the repository, please create a feature branch off of the dev branch. Once you're finished working on the feature, make a pull request to merge it into dev. Please make sure that every pull request has passed the build checks, which appear just before the "Merge pull request" button in github.

Code Style

Checkout the code and comments in /components/ExampleComponent for an example functional React component, .scss file, and tests.

React

  • Most components should be stateless and use the functional component pattern
  • If you need a stateful component, use ES6 classes
  • Always use PropTypes for all props
  • Use classnames for dynamic classes. See ExampleComponent for an example.

JavaScript

  • Make sure your variable names are easy to understand and descriptive. No acronyms, except for common ones like i or err.
  • Use lodash and functional JavaScript if it makes the code clearer.
  • Please use ES2015 syntax whenever possible
  • Specific rules are enforced via .eslintrc.json
  • Run npm run lint to check your code against the linter

SCSS Files

  • This repository uses flexbox for arranging content
  • The use of any extra CSS libraries should be discussed with the team
  • Use SCSS syntax, but do not overly nest
  • Use 2 spaces for indentation
  • Use variables, mixins, and classes as much as possible from our style guide
  • To include variables from the style guide mentioned above, place @import 'topcoder/tc-includes;' at the top of your .scss file. Locally, you can look in ./node_modules/appirio-styles/styles/topcoder/_tc-colors.scss to find many colors already defined (e.g. #A3A3AE => $accent-gray)
  • When adding media queries, nest them inside the element, rather than creating a new section
@import 'topcoder/tc-includes;'

$my-local-var: 50px;

.box {
  height: $my-local-var;
  width: 50px;
  color: $medium-gray;
  @media screen and (min-width: 768px) {
    height: 100px;
    width: 100px;
    color: $dark-gray;
  }

  .inside-box {
    font-size: 14px;
    @media screen and (min-width: 768px) {
      font-size: 18px;
    }
  }
}

Writing Tests

  • npm test will run the current tests
  • Place your test files in the same directory as the component it's testing
  • Test files should be named ComponentName.spec.js

Recommended Developer Tools

Syntax highlighting for ES6 and React JSX

  • Install babel via the package manager in Sublime Text
    • Note: Sublime Text 3 is required for this plugin
  • Set the plugin as the default syntax for a particular extension
    • Open a file with the .js extension
    • Select View from the menu
    • Then Syntax -> Open all with current extension as...
    • Then Babel -> JavaScript (Babel)
    • Repeat for any other extensions, e.g. .jsx

Recommended Theme

  • Install Oceanic Next Color Theme via the Sublime Text package manager.
  • Add the following to Sublime Text -> Preferences -> Settings-User (⌘ + , on Mac)
{
  "color_scheme": "Packages/Oceanic Next Color Scheme/Oceanic Next.tmTheme",
  "theme": "Oceanic Next.sublime-theme"
}

Automatic JavaScript linting in Sublime Text

  • Install SublimeLinter following the instructions under "Installing via Package Control"
  • Install SublimeLinter-eslint with the package manager. The package is called SublimeLinter-contrib-eslint

Code expander

  • Examples:
    • div.cool-class becomes <div className="cool-class"></div>
    • a becomes <a href=""></a>
  • Install Emmet via Sublime Text package manager
  • Configure Emmet to work with React, e.g. classes expand to className instead of class
  • Follow the instructions under Get Emmet working
    • Note: Add the last snippet of code to reg_replace.sublime-settings by navigating to Sublime Text -> Preferences -> Package Settings -> Reg Replace -> Settings-User

Using the react-components repository in your app

Install

npm install appirio-tech-react-components