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

@ultimaker/ultimaker.com-designsystem

v47.0.0

Published

Ultimaker.com design system for vue components

Downloads

43

Readme

Ultimaker.com Designsystem

Prerequisites

  • Git client of your choice
  • NodeJS (Installation through brew(macos)/chocolatey(windows) recommended)

Install

  • Clone project from https://github.com/Ultimaker/Ultimaker.com-designsystem
  • Run npm i to install NPM dependencies
  • Test project with npm run unit

NPM Commands

  • storybook: Storybook development environment

  • test or unit: Execute all tests in browserstack (first create test/karma.conf.json)

  • unit:chrome: Execute all unit tests in headless chrome

  • unit:debug: Execute all test continuously, attach your own browser

  • build: Build amd module

  • build:dev: Builds an amd module for local testing

  • lint: Lints all javascript

  • build-storybook: Generate static storybook environment

Hygen Timesavers

We’ve added hygen, the scalable code generator that saves you time, to the stack so that you can quickly generate a new component using our component standard, which is reflected in the component structure outputted by the command.

Below is an example of issuing the command to create an atom component called my-component.

npx hygen modules component --name my-component --type atom

options - type

  • atom
  • molecule
  • organism

Prettier

To add and run prettier against a component use the following command adjusting the component directory path as necessary

npx prettier --write --insert-pragma --require-pragma=false src/js/components/molecules/cards/card-article/**/*.{ts,scss,html}

Git Hooks

git hook management has been setup using using husky. current hooks:

  • pre-push

SVG Icons

SVG icons reside individually in the designsystem in the /src/assets/icons directory. Webpack combines them into one sprite file, which is placed in the dist/static/icons folder. The UX Harmonization team is working on a new icon set, but for now, this is our icon set. Also, once we have one repo that serves as our frontend application another way to serve the SVG icon set can be investigated, but for now, the following strategy is used:

frontend

Updating frontend will need to happen manually. The SVG sprite in the designsystem dist/static/icons folder should be placed in the src/index.template.html file in the frontend project.

legacy

Updating legacy will need to happen manually. The SVG sprite in the designsystem dist/static/icons folder should be placed in the src/SiteBundle/Resources/views/layout.html.twig and src/SiteBundle/Resources/views/popup_layout.html.twig files in the legacy project.

storybook

Updating storybook need to happen manually. The SVG sprite in the designsystem dist/static/icons folder should be placed in the .storybook/preview-body.html file in the designsystem project.