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

@intellyo/intellyo-components

v12.4.1

Published

Intellyo Application Design System

Downloads

7

Readme

Intellyo's Application Design System

Intellyo's frontend framework (or FeF as we call it), written in React. We created this repository to organise our components and have a consistent design style throughout our applications.

Applications using FeF

Component list:

Here you can find each of our components:

E2E tests usage:

You can find the README.md in the e2e folder.

Big Thanks

Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs

License

MIT

Deployment and release

hubot is here to rescue us all

Release

hubot ci build intellyo-application-design-system@patch

Instead of patch you can use:

  • premajor
  • major
  • preminor
  • minor
  • prepatch
  • patch
  • prerelease

This will create a new patch release and it'll deploy it automatically.

Deployment

Deployment is handled by CircleCI, if you are deploying which was a patch, minor or major the new version will be published to the npm repository and rolled out to http://intellyo.design/. If you are deploying a prerelease, prepatch, preminor, premajor then it'll be published to npm but won't be rolled out http://intellyo.design/.

If you want to manually deploy a version, or roll back to previous one, you can do it:

hubot ci deploy [email protected]

Force build

If the build fails because there's a broken e2e test, unit test or a lint issue you still can build a new version, you just need to force it. Force build still runs the tests but independently of their result the build will be marked as green.

hubot ci force build intellyo-application-design-system@prepatch

To prevent any accidental executions you have to supply the daily villain (since you are doing a dangerous thing), but hubot is here to help you:

oroce: hubot ci force build intellyo-application-design-system@prepatch

hubot: oroce: You are trying to be a villain, aren't you?
       It's ok from time to time to be one, but you gotta know the safe word, today's one is: 
       *Scream*
       hubot ci force build intellyo-application-design-system@prepatch daily-villain=Scream

The daily villain is changed -as you'd guess- every day.

Since you used force build, probably your branch was failing. Even though we'll try to autodeploy it, it'll too. So you need to force deploy it.

Force deploy

If autodeploy fails, you can manually force it.

hubot ci force deploy [email protected]

You will supply the daily villain again, similarly to force build.

Build from feature branch

Sometimes you want to create a new release from a feature branch (great for an rc, prelease, premajor), you can use both build and force build to do that as well.

hubot ci build intellyo-application-design-system#feat/breaking-change@prepatch

or

hubot ci force build intellyo-application-design-system#feat/breaking-change@prepatch