npmpackage.info

Gathering detailed insights and metrics for ngx-widgets

Gathering detailed insights and metrics for ngx-widgets

ngx-widgets - 3.2.0 | npmpackage.info

ngx-widgets

A collection of Angular components and useful bits that are commonly used.

3.2.0

4

Apache-2.0

TypeScript

908.00 B

Installations

npm install ngx-widgets

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

8.3.0

Node Version

8.12.0

NPM Version

6.4.1

Score

54.3

Supply Chain

83.9

Quality

78.5

Maintenance

50

Vulnerability

94.3

License

Pull Requests

Open

0

Total

142

Closed

18

Merged

124

Issues

Open

7

Total

18

Closed

11

Releases

93

v3.2.0

Updated on Nov 14, 2018

v3.1.5

Updated on Oct 18, 2018

v3.1.4

Updated on Oct 10, 2018

v3.1.3

Updated on Sep 27, 2018

v3.1.2

Updated on Sep 07, 2018

v3.1.1

Updated on Sep 04, 2018

View All 93 releases

Languages

6

TypeScript

JavaScript

CSS

HTML

Shell

Ruby

TypeScript (40.95%)

JavaScript (38.64%)

CSS (11.21%)

HTML (4.85%)

Shell (3.46%)

Ruby (0.89%)

Developer

fabric8-ui

Download Statistics

Total Downloads

133,899

Last Day

2

Last Week

7

Last Month

365

Last Year

3,674

GitHub Statistics

Apache-2.0 License

4 Stars

415 Commits

18 Forks

19 Watchers

2 Branches

27 Contributors

Updated on Jan 28, 2023

Bundle Size

2.55 kB

Minified

908.00 B

Minified + Gzipped

Bundlephobia

Maintainers

4

View All 27 Contributors

Package Meta Information

Latest Version

3.2.0

Package Id

ngx-widgets@3.2.0

Unpacked Size

777.61 kB

Size

197.56 kB

File Count

163

NPM Version

6.4.1

Node Version

8.12.0

Total Downloads

Cumulative downloads

Total Downloads

133,899

Last Day

0%

2

Compared to previous day

Last Week

-97.4%

7

Compared to previous week

Last Month

-37.5%

365

Compared to previous month

Last Year

40.7%

3,674

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

2

moment patternfly-ng

Peer Dependencies

6

@angular/animations @angular/common @angular/core @angular/forms @angular/router rxjs

Dev Dependencies

127

@angular/animations @angular/common @angular/compiler @angular/compiler-cli @angular/core @angular/forms @angular/http @angular/platform-browser @angular/platform-browser-dynamic @angular/platform-server @angular/router @krux/condition-jenkins @ngtools/webpack @types/core-js @types/jasmine @types/lodash angular2-load-children-loader angular2-router-loader angular2-template-loader assets-webpack-plugin autoprefixer child_process clean-css clean-webpack-plugin codelyzer copy-webpack-plugin copyfiles core-js cpy-cli css-loader css-to-string-loader cz-conventional-changelog del exports-loader expose-loader extract-text-webpack-plugin file-loader gh-pages gulp gulp-changed gulp-cssmin gulp-less gulp-rename gulp-replace gulp-sourcemaps gulp-string-replace gulp-stylelint html-loader html-minifier html-webpack-plugin htmlhint-loader husky imports-loader istanbul-instrumenter-loader jasmine jasmine-core json-loader json-stringify karma karma-chrome-launcher karma-cli karma-coverage karma-firefox-launcher karma-htmlfile-reporter karma-jasmine karma-jasmine-html-reporter karma-mocha karma-mocha-reporter karma-phantomjs-launcher karma-remap-coverage karma-remap-istanbul karma-safari-launcher karma-sourcemap-loader karma-typescript karma-webpack less less-loader less-plugin-autoprefix markdown-it mini-css-extract-plugin mocha ng-router-loader npm-run-all null-loader opt-cli optimize-js-plugin parse5 path patternfly phantomjs-prebuilt postcss-loader precss protractor raw-loader reflect-metadata resolve-url-loader rimraf run-sequence rxjs rxjs-compat rxjs-tslint script-ext-html-webpack-plugin semantic-release source-map-loader style-loader stylelint stylelint-webpack-plugin stylus to-string-loader ts-helpers ts-loader ts-node tslint tslint-loader typedoc typedoc-webpack-plugin typescript url-loader webpack webpack-bundle-analyzer webpack-cli webpack-dev-middleware webpack-dev-server webpack-dll-bundles-plugin webpack-md5-hash webpack-merge zone.js

ngx-widgets

A collection of Angular components and other useful things to be shared.

You can see how it is used in our application here.

The system we build is composed of several components existing in separate repos but sharing common components, directives, and pipes. These widgets were extracted to provide a shared set of services.

Getting started:

This library does not run on it's own. It must be imported.

npm install ngx-widgets

There are several services and a couple of models used by them available.

container-toggle
dialog
dropdown
editable
icon
infinitescroll

Building it

Install the dependencies:

npm install

If you need to update the dependencies you can reinstall:

npm run reinstall

Run the tests:

npm test

Run Stylelint checks

'gulp lint-less'

Library Build

Production

To build ngx-widgets as a npm library, use:

npm run build

Whilst the standalone build uses webpack the library build uses gulp.

The created library is located in dist. You shouldn't ever publish the build manually, instead you should let the CD pipeline do a semantic release.

Development

To build ngx-widgets as an npm library and embed it into a webapp such as fabric8-ui, you should:

Run npm run watch:library in this directory. This will build ngx-widgets as a library and then set up a watch task to rebuild any ts, html and less files you change.
In the webapp into which you are embedding, run npm link <path to ngx-widgets>/dist-watch --production. This will create a symlink from node_modules/ngx-widgets to the dist-watch directory and install that symlinked node module into your webapp.
Run your webapp in development mode, making sure you have a watch on node_modules/ngx-widgets enabled. To do this using a typical Angular Webpack setup, such as the one based on Angular Class, just run npm start. You will have access to both JS sourcemaps and LESS sourcemaps if your webapp is properly setup.

Note that fabric8-ui is setup to do reloading and sourcemaps automatically when you run npm start.

Continuous Delivery & Semantic Relases

In ngx-widgets we use the semantic-release plugin. That means that all you have to do is use the AngularJS Commit Message Conventions (documented below). Once the PR is merged, a new release will be automatically published to npmjs.com and a release tag created on github. The version will be updated following semantic versionning rules.

Commit Message Format

A commit message consists of a header, body and footer. The header has a type, scope and subject:

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

The header is mandatory and the scope of the header is optional.

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.

Revert

If the commit reverts a previous commit, it should begin with revert: , followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the SHA of the commit being reverted.

Type

If the prefix is feat, fix or perf, it will always appear in the changelog.

Other prefixes are up to your discretion. Suggested prefixes are docs, chore, style, refactor, and test for non-changelog related tasks.

Scope

The scope could be anything specifying place of the commit change. For example $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, etc...

Subject

The subject contains succinct description of the change:

use the imperative, present tense: "change" not "changed" nor "changes"
don't capitalize first letter
no dot (.) at the end

Body

Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.

Footer

The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.

Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.

A detailed explanation can be found in this document.

Based on https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit

Examples

Appears under "Features" header, pencil subheader:

feat(pencil): add 'graphiteWidth' option

Appears under "Bug Fixes" header, graphite subheader, with a link to issue #28:

fix(graphite): stop graphite breaking when width < 0.1

Closes #28

Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:

perf(pencil): remove graphiteWidth option

BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reason.

The following commit and commit 667ecc1 do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header.

revert: feat(pencil): add 'graphiteWidth' option

This reverts commit 667ecc1654a317a13331b17617d973392f415f02.

Commitizen - craft valid commit messages

Commitizen helps you craft correct commit messages. Install it using npm install commitizen -g. Then run git cz rather than git commit.

Validate-commit-msg - validate commit messages

The validate-commit-msg githook checks for invalid commit messages.

Empty State

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

5

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

SAST

Determines if the project uses static code analysis.

Score

3.9

/10

Last Scanned on 2025-06-23

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.