NG Alternative (Fork NgBootstrap) - Angular 2 directives specific to Bootstrap 4

Welcome to the Angular 2 version of the Angular UI Bootstrap fork library. This library is being built from scratch by the ui-bootstrap team, but I did a fork with features in alternative version. We are using TypeScript and targeting the Bootstrap 4 CSS framework.

It uses ng-bootstrap alpha 17 with Bootstrap 4.alpha5 since here we´ll do update with new features and bug fixes.

As with Bootstrap 4 and Angular 2, this library is a work in progress. Please check out our list of issues to see all the things we are implementing. Feel free to make comments there.

Demo

View all the directives in action at https://ng-bootstrap.github.io

Dependencies

• Angular 2 (tested with 2.3.1)
• Bootstrap 4 (tested with 4.0.0-alpha.5)

Installation

After installing the above dependencies, install ng-bootstrap via:

npm install --save @stephanoapiolaza/ng-alternative

Once installed you need to import our main module:

import {NgbModule} from '@stephanoapiolaza/ng-alternative';

The only remaining part is to list the imported module in your application module. The exact method will be slightly different for the root (top-level) module for which you should end up with the code similar to (notice NgbModule.forRoot()):

import {NgbModule} from '@stephanoapiolaza/ng-alternative';

@NgModule({
  declarations: [AppComponent, ...],
  imports: [NgbModule.forRoot(), ...],  
  bootstrap: [AppComponent]
})
export class AppModule {
}

Other modules in your application can simply import NgbModule:

import {NgbModule} from '@stephanoapiolaza/alternative';

@NgModule({
  declarations: [OtherComponent, ...],
  imports: [NgbModule, ...], 
})
export class OtherModule {
}

SystemJS

If you are using SystemJS, you should also adjust your configuration to point to the UMD bundle.

In your systemjs config file, map needs to tell the System loader where to look for ng-bootstrap:

map: {
  '@stephanoapiolaza/ng-alternative': 'node_modules/@stephanoapiolaza/ng-alternative/bundles/ng-bootstrap.js',
}

Supported browsers

We support the same browsers and versions supported by both Bootstrap 4 and Angular 2, whichever is more restrictive. See this for up-to-date Angular 2 browser support.

• Chrome (45+)
• Firefox (40+)
• IE (9+) (but see Bootstrap 4's notes on IE9)
• Edge (20+)
• Safari (7+)

Contributing to the project

Please check the CONTRIBUTING.md doc for contribution guidelines.

Getting Help

Please, do not open issues for the general support questions as we want to keep GitHub issues for bug reports and feature requests. You've got much better chances of getting your question answered on StackOverflow where maintainers are looking at questions tagged with ng-bootstrap.

StackOverflow is a much better place to ask questions since:

• there are hundreds of people willing to help on StackOverflow
• questions and answers stay available for public viewing so your question / answer might help someone else
• SO voting system assures that the best answers are prominently visible.

To save your and our time we will be systematically closing all the issues that are requests for general support and redirecting people to StackOverflow.

You think you've found a bug?

Oh, we are ashamed and want to fix it ASAP! But before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will systematically ask you to provide a minimal reproduction scenario using http://plnkr.co. Having a live, reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like:

• version of Angular used
• version of this library that you are using
• 3rd-party libraries used, if any
• and most importantly - a use-case that fails

A minimal reproduce scenario using http://plnkr.co/ allows us to quickly confirm a bug (or point out coding problem) as well as confirm that we are fixing the right problem. The best part is that you do not need to create plunks from scratch - you can fork one from our demo page.

We will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience users often find coding problems themselves while preparing a minimal plunk. We understand that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate the problem before we can fix it.

Unfortunately we are not able to investigate / fix bugs without a minimal reproduce scenario using http://plnkr.co, so if we don't hear back from you we are going to close an issue that don't have enough info to be reproduced.

Code of Conduct

Please take a moment and read our Code of Conduct