New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

cloudify-ui-common-frontend

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

cloudify-ui-common-frontend

Common Cloudify UI frontend library

latest
Source
npmnpm
Version
2.1.0
Version published
Weekly downloads
43
-50%
Maintainers
1
Weekly downloads
 
Created
Source

Cloudify UI Common Frontend

npm

This package contains common static assets (images, fonts, styles, etc.) as well as TypeScript library with functions reusable across Cloudify UI frontend applications.

Installation

npm install cloudify-ui-common-frontend

Usage

To load the package into your environment use one of the below presented option for getting icons module.

ES module

import { icons } from 'cloudify-ui-common-frontend';

CommonJS

const icons = require('cloudify-ui-common-frontend').icons;

Browser

<script src="https://cdn.jsdelivr.net/npm/cloudify-ui-common-frontend@1.0.0"></script>

Check jsDelivr home page for details about the URL format. You can get specific version and/or specific file from the package.

Documentation

  • Fonts - shared common fonts
  • Images - shared common images
  • Styles - shared CSS, SCSS stylesheets

Development

Development environment is set up to enforce good practices in TS development (static code analysis, style formatting, code coverage check).

Some general guidelines for different type of assets are listed below.

Static files

  • add new assets to dedicated folder for specific type
  • when removing assets verify that it is not used anywhere
  • if relevant and possible add documentation on asset usage (eg. in README.md file in the same folder as asset)
  • there is Cloudify Brandbook containing Cloudify Brand Guidelines we should follow creating new resources

TypeScript library

  • add new code to src folder
  • remember to export new files in src/index.ts (otherwise the new code will not be available in the distribution package)
  • build: npm run build (production build) or npm run dev (automatic rebuilding)
  • test: npm run test (unit testing with Jest testing framework), npm run lint (static analysis, code style check) and npm run check-types (TypeScript types check)
  • document your code (we are using JSdoc block tags)

FAQs

Package last updated on 03 Aug 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts