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

bidcoreng

v1.0.2

Published

Bidcore library to deal with complex data and autogenerate tables and forms

Downloads

2

Readme

Installation

  1. Clone or download the library to your computer.

  2. Using the terminal cd go to the bidcoreng folder.

  3. Compile in root folder.

yarn install
yarn build
// OR use the npm commands
npm install
npm run build

##NOTE: If this error arises npm ERR! Error: EPERM: operation not permitted, scandir please run npm cache verify (https://github.com/npm/npm/issues/17747)

  1. Run tests often with yarn test

  2. Run tslint often with yarn lint

  3. Connect the library to your project with

yarn link
// OR use the npm commands
npm link
  1. cd to your project and run
yarn link bidcoreng
// OR use the npm commands
npm link bidcoreng
  1. Now you can run with
yarn start
// OR use the npm commands
npm run start

From now on you do not need to link your library again (unless a new dependency is installed), but caution after changing something in the library and saving, to see your changes reproduce steps 3. and 7..

{-IMPORTANT-} Sometimes after changes in the library if one of the following errors occur

  • Can not find AllLibraryServicesListed OR
  • ENOENT not index.js file exists

The consumer project must be rerun!

Changes in your project are live updated not needing to rerun the app.

Connect to your project

(Be sure to also check https://git.bidcore.de/tsioris/bidcoreNG/wikis/fixing-error )

From your Angular AppModule:

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppComponent } from './app.component';

// Import your library
import { NameOfTheModuleYouWantToUse } from 'bidcoreng';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,

    // Specify your library as an import
    NameOfTheModuleYouWantToUse
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Usage

Once your library is imported, you can use its components, directives and pipes in your Angular application:

<!-- You can now use your library component in app.component.html -->
<h1>
  {{title}}
</h1>
<exampleComponent></exampleComponent>

Services must be imported into the app module as well.

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppComponent } from './app.component';

import { NameOfTheModuleYouWantToUse } from 'bidcoreng';

// Import your library
import {  
    TableExpandableRowService,
    BidModalService,
    CustomValidators,
    OptionsValidatorService,
    BidListFormService,
    StackViewService } from 'bidcoreng';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,

    NameOfTheModuleYouWantToUse
  ],
  providers: [
    // Specify your service as a provider
    TableExpandableRowService,
    BidModalService,
    CustomValidators,
    OptionsValidatorService,
    BidListFormService,
    StackViewService
],
  bootstrap: [AppComponent]
})
export class AppModule { }

and to use the service inside your components you finally need to import it in each component needing it, or having as Child nodes bidcoreNG components requiring it

    import { RequiredLibraryService } from 'bidcoreng';
    constructor(private libraryService: typescript){}