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

@medrecord/ui-components

v1.0.0

Published

[Components Demo](https://master-storybook.medvision360.org/)

Downloads

8

Readme

MedrecordUiComponents

Components Demo

Installation

npm i @medrecord/ui-components @medrecord/frontend-translations-middleware

Connect styles to you root styles file

@import "~@medrecord/ui-components/components";

Assets

For correct components work you should connect fonts, icons and translations.

angular.json

 "build": {
  "builder": "@angular-devkit/build-angular:browser",
  "options": {
    "allowedCommonJsDependencies": [
      "@medrecord/frontend-translations-middleware",
      "lodash",
      "lodash/get",
      "lodash/uniqBy",
      "lodash/toString",
      "moment-timezone",
      "moment-range"
    ],
    ....
    "assets": [
      ...
      {
        "glob": "**/*",
        "input": "node_modules/@medrecord/ui-components/client-styling/images/",
        "output": "/client-styling/images/"
      },
      {
        "glob": "**/*",
        "input": "node_modules/@medrecord/ui-components/fonts/",
        "output": "/client-styling/fonts/"
      },
      {
        "glob": "**/*",
        "input": "node_modules/@medrecord/ui-components/medrecord-i18n/",
        "output": "/assets/medrecord-i18n/"
      }
      ...
    ],
   ...
  },
...

Import MedrecordUiComponentsModule and HttpClientModule in root module of your application.

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    AppRoutingModule,
    ...
    MedrecordUiComponentsModule,
    TranslationMiddlewareModule.forRoot()
    HttpClientModule,
    ...
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Translations

Library uses translations what are managed by @medrecord/frontend-translations-middleware and connected as assets. For correct components work library should be installed and connected in root module.

Troubleshooting

Take into account that starting with version 10, Angular now warns you when your build pulls in one of these bundles. If you’ve started seeing these warnings for your dependencies, let your dependency know that you’d prefer an ECMAScript module (ESM) bundle. Here is an official documentation - Configuring CommonJS dependencies

Add into your angular.json


"architect": {
"build": {
  "builder": "@angular-devkit/build-angular:browser",
  "options": {
    ...
    "allowedCommonJsDependencies": [
      "moment-timezone",
      "moment-range",
      "lodash/get",
      "lodash/uniqBy"
    ],
    ...

We are using i18n and Angular 9 introduced a global $localize() function that needs to be loaded. Please run ng add @angular/localize from the Angular CLI. (For non-CLI projects, add import '@angular/localize/init'; to your polyfills.ts file.