Bootstrap-Wizard | Uses Bootstrap and JQuery to provide | Frontend Framework library

I got this error while setup my react app using the webpack and babel. I try to change the version of babel but still getting the same error. I'm not getting where's the problem.

In my application working with angular js2 standalone. After integrating angular js2 build to spring boot web app files for deploy as single war. then getting error like this

I tried two senarioes 1) add npm intall and npm run build add as maven exucution goals. 2)Angularjs build manually by using commands that build out out copy to web app directry then build war. These war put inito my local host then get these js missing problem. I'm new in angular2 My working environment Node : v8.1.2 npm -: v5.0.3 anular: 1.2

I am using xterm in Angular5. But it is throwing an error while running.

When i run ng serve so it throws an error like this

ERROR in node_modules/xterm/typings/xterm.d.ts(10,1): error TS1084: Invalid 'reference' directive syntax

Here is my package.json file

I have a form in multiple steps inside a modal window using Twitter Bootstrap Wizard Plugin, it shows well the steps and if I click on one of those steps change to other steps, but when I push "Next" or "Previous" don't do nothing.

I trying adding:

I am using this plugin to create a Wizard like interface.

https://github.com/jeffreypolk/bootstrap-wizard

Is there a way to add a method that support going to any step? Ex: If I am on Step 2, and click "Next", I would like to go to Step 4. In the same way, if I am on Step 4, but clicked on "Previous", I would like to go to Step 2, because that's how I got here.

I am working on writing a method for this, but looking for some ideas.

UPDATE: After digging further, I tried a regular bootstrap 4 dropdown, with the same result. The dropdown does not open. I believe this means it can't be a problem with the selectpicker class or the bootstrap-select dependency specifically. Also has the same issue when using ng-bootstrap dropdown.

UPDATE 2: Ngx-dropdown does work, and is the only dropdown I can find that still works, but it operates differently. I'm hoping that helps figure out why.

UPDATE 3: Have confirmed this is not just an issue while working in Chrome. Same issue in firefox and safari.

After upgrading to Angular 6, the bootstrap-select element no longer drops down unless I remove the class="selectpicker". The little dropdown arrow no longer shows up either.

I've tried downgrading the bootstrap selectpicker, upgrading to the latest version, checking if jquery is updated, making sure selectpicker has the dependencies and versions installed it needs (jquery greater than 1.8.1 I think)

It also does not work when trying to manually force a dropdown. (see below)

With class="selectpicker"

Without class="selectpicker"

Before updating to angular 6 and updating dependencies (pulled from production)

Problem shown with both bootstrap-select and regular bootstrap 4 dropdown.

Forcing a dropdown via button:

With ngx-select-dropdown working:

The code used for a given select picker:

When I tried to run ng serve it runs without any error, but when I tried to create a production build using 'ng build --prod' it stopped with error below. I tried to tweak with the version still no success. Then some other issue occurred like other API version compatibility issue. Any help will be highly appreciated.

ERROR in ./src/main.ts Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in 'D:\000PS\workspace_ui\dashboard\src' ERROR in Error: Metadata version mismatch for module D:/000PS/workspace_ui/dashboard/node_modules/ngx-pipes/src/app/index.d.ts, found version 4, expected 3 at StaticSymbolResolver.getModuleMetadata (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler\bundles\compiler.umd.js:25755:34) at StaticSymbolResolver._createSymbolsOf (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler\bundles\compiler.umd.js:25543:46) at StaticSymbolResolver.getSymbolsOf (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler\bundles\compiler.umd.js:25524:14) at D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler\bundles\compiler.umd.js:24381:30 at Array.forEach () at extractProgramSymbols (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler\bundles\compiler.umd.js:24380:79) at AotCompiler.analyzeModulesAsync (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler\bundles\compiler.umd.js:23936:47) at CodeGenerator.codegen (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler-cli\src\codegen.js:32:14) at Function.NgTools_InternalApi_NG_2.codeGen (D:\000PS\workspace_ui\dashboard\node_modules\@angular\compiler-cli\src\ngtools_api.js:73:30) at _donePromise.Promise.resolve.then (D:\000PS\workspace_ui\dashboard\node_modules\@ngtools\webpack\src\plugin.js:428:58) at at process._tickCallback (internal/process/next_tick.js:188:7)

Please find package.json for reference:

I've been searching for a solution to this weird behavior with no luck.

• There are no errors in the angular 4 console or the javascript console
  • Using Angular CLI (Angular 4)

I'm getting extremely weird behavior with the angular router. I'm attempting to load a child route, which has it's own module, from the parent AppModule. The route is at /products

At the /products module (products.module.ts): I have 3 routes:

1. /products/overview
2. /products/intro [redirected to from /products]
3. /products/product/:product

The products module is supposed to have it's own navbar UNDER the global AppModule's navbar, which is above the router-outlet in the products.component.html component template.

The main problem: When I load the page (not using an angular routerLink) to /products:

• both navbars are visible
• the page that is LOADED (ex /intro) has the navbar visible, but the child component (IntroComponent) is NOT visible
• HOWEVER, when I navigate to any other subroute within the /products module routes, (ex /overview or /product/:product): it renders just fine. So whatever route is loaded on a full page refresh is not visible.

The weirdest part: When I LOAD the page (refresh) on a route that isn't /products (ex /home) and then use the main navbar to navigate to /products:

• The navbar is not visible ?????
• The sub component (ex /intro component) IS visible

This has been causing me a great deal of hell for the past few days.

Now, some code:

app.module.ts [main AppModule]

I have used this plugin: http://vinceg.github.io/twitter-bootstrap-wizard/

at last, the next button is becoming is disabled can anyone help how can I enable it.?