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

@engie-group/fluid-design-system-angular

v2.6.2

Published

Fluid Design System Angular

Downloads

690

Readme

Angular Fluid Design System by ENGIE

DISCLAIMER

When installing the package via NPM or importing it via CDN, we recommend fixing the version with the exact package version to avoid breaking change affecting your live website. With never-ending topics like Accessibility and Brand guidelines, we sometimes have to include some minor breaking changes in some minor versions.

Installation

Install the package inside your application:

npm install --save-exact @engie-group/fluid-design-system-angular

If you use deprecated components or need our css reboot, you will need to install and use some styles from the @engie-group/fluid-4-deprecated package.

Please refer to the @engie-group/fluid-4-deprecated README.md for more information.

npm install @engie-group/fluid-4-deprecated

1. Font & Styles

<!--Not necessary if you already import Lato and don't use Material icons-->
<link href="https://fonts.googleapis.com/css?family=Material+Icons|Lato:300,400,700,900&amp;display=swap" rel="stylesheet"/>

// In angular.json in build.styles of your project you'll need to import the fluid css variables and the fluid icons (ONLY if you're planning on using them) 
"styles": [
  // Imports tokens, needed for components
  "node_modules/@engie-group/fluid-design-tokens/lib/css/tokens.css", 
  // Sets the correct font properties for you website
  "node_modules/@engie-group/fluid-design-system/lib/base.css", 
  // Only if you want to use engie icons
  "node_modules/@engie-group/fluid-design-system/lib/components/icon/fluid.css",
  // Only if you use deprecated components
  "node_modules/@engie-group/fluid-4-deprecated/tokens/lib/css/tokens.css", 
], 

2. Enabling the animations module

For application bootstrapped with the bootstrapApplication() function (usually in main.ts), add the provideAnimations() function in the provider list:

import {provideAnimations} from '@angular/platform-browser/animations';

bootstrapApplication(AppComponent, {
  providers: [
    provideAnimations(),
  ]
});

Or for NgModule based applications import BrowserAnimationModule, which introduces the animation capabilities into your module:

import {BrowserAnimationsModule} from '@angular/platform-browser/animations';

@NgModule({
    declarations: [],
    imports: [
        BrowserAnimationModule
    ],
    exports: [],
    providers: []
})
export class AppModule {
}

See Angular documentation

Using a component in your codebase

Fluid components are standalone, when you need to use them, you must import them in the component's imports or the module's imports where they are used:

import {NgModule} from "@angular/core";
import {ButtonComponent} from '@engie-group/fluid-design-system-angular'

@NgModule({
  imports: [ButtonComponent]
})
export class AppModule {}

or

import {Component} from "@angular/core";
import {ButtonComponent} from '@engie-group/fluid-design-system-angular'

@Component({
  template: '<nj-button>Label</nj-button>',
  imports: [ButtonComponent]
})
export class CustomComponent {}

You can use the Imports section of each component documentation page to know what to import for the component to work correctly.

How to Contribute to new Components

  • Create a component folder inside src/components:

    src/components - / component-name.component.html - / component-name.component.scss / component-name.component.ts / component-name.component.spec.ts -

    Make sure that your component is a standalone component

  • Update src/public-api.ts by exporting your component

  • Create a component StoryBook story inside fluid-doc-angular package: src/stories/component-name/component-name.stories.tsx

Components development state

You can check our state of development on our Components status page

Troubleshooting

If you encounter any issues while setting up Fluid Design System, please create an issue or a request on our library git repository.