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 🙏

© 2025 – Pkg Stats / Ryan Hefner

beyond-iqoa-shared-ng

v0.0.0

Published

This project regroups a library of shared components that can be used within Angular application/library and a showcase application to see components in action.

Readme

BeyondIqoaSharedNg

This project regroups a library of shared components that can be used within Angular application/library and a showcase application to see components in action.

Showcase

To see the components in action:

npm i
npm run link
npm run bs

Then go to localhost:4200

UI components

Color picker

To use the color picker in your application/library, import IqoaColorPickerModule from @sixense/beyond-iqoa-shared-ng, then use it in your template like any other FormControl:

<iqoa-color-control [formControl]="colorPickerControl"></iqoa-color-control>
<iqoa-color-control formControlName="color"></iqoa-color-control>

Shared functionnalities

Translations

In order to use the shared translations service, you need to provide the translations or your application, by merging them with the existing translations. You can do so by loading your translations in your main module.

In your app's module or library's main module:

export function appInitLoadTranslations(iqoa: IqoaTranslateService): () => Promise<void> {
    iqoa.setTranslation('fr-fr', frFR);
    iqoa.setTranslation('en-en', enGB);
    return () => Promise.resolve();
}

@NgModule({
    ...
    providers: [
        ...
        {
            provide: APP_INITIALIZER,
            useFactory: appInitLoadTranslations,
            deps: [IqoaTranslateService],
            multi: true,
        },
    ],
})

You can then use the service or the pipe by importing IqoaTranslateModule into your module.

Then, in your .ts:

import { IqoaTranslateService } from '@sixense/beyond-iqoa-shared-ng';
constructor(
    private readonly iqoaTranslateService: IqoaTranslateService,
) {
    const translated = this.iqoaTranslateService.translate('common.my_translation');
}

Or in your .html:

<h3>
    {{ 'common.my_translation' | iqoaTranslate }}
</h3>

Error handling

In order to use the shared error handler service, you need to provide IqoaGlobalErrorHandlerService as an HTTP_INTERCEPTOR and to configure your app this way.

export function globalErrorHandlerConfig(env: EnvironmentService): IqoaErrorHandlerConfig {
    return { apiUrl: env.apiUrl || '', errorCodePrefix: 'YOUR_APP_CODE' };
}

@NgModule({
    ...
    providers: [
        ...
        {
            provide: HTTP_INTERCEPTORS,
            useClass: IqoaGlobalErrorHandlerService,
            multi: true,
        },
        {
            provide: IQOA_ERROR_HANDLER_CONFIG,
            useFactory: globalErrorHandlerConfig,
            deps: [EnvironmentService],
            multi: true,
        },
    ],
})

apiUrl will filter the requests that should be handled for your app. errorCodePrefix will be used to generate an error message telling that your API is unreachable and to filter errors (the errors API is sending should have a property "code" that contains this errorCodePrefix).

If you have added your translations like explained above, IqoaGlobalErrorHandlerService will use your translations to display errors in a comprehensive way. Error messages will be displayed in a coherent way through your app, and all you need to do then is to handle errors where you want, like for example if you want to highlight a field in a form.