jagonalez / aurelia-navigation-menu Goto Github PK

By including this:

import { NavigationMenu } from 'aurelia-navigation-menu';

I get the following error:

TypeError: System.config is not a function
at Object.eval (config.js?af18:1)
at eval (aurelia-navigation-menu:141)
at Object.aurelia-navigation-menu (app.bundle.js:5827)
at webpack_require (app.bundle.js:20)
at WebpackLoader.eval (aurelia-loader-webpack.js?b873:176)
at step (aurelia-loader-webpack.js?b873:36)
at Object.eval [as next] (aurelia-loader-webpack.js?b873:17)
at eval (aurelia-loader-webpack.js?b873:11)
at new Promise ()
at __awaiter (aurelia-loader-webpack.js?b873:7)

The sample app works fine.

Note: I don't have a code sample yet, as the problem is not showing up when I try to repro using the example code you provided.

I'm having an issue with implementing the navmenu with a larger codebase.

Third level items are showing up, but with the incorrect href. From debugging, it seems that where nav.href is set in navigation-menu.js, navModel.href is undefined. The hrefs are showing up like 'undefined/mynestedpath' instead of 'mysection/mynestedpath'

Note that I am not blocking activate for my app on this.navigationMenu.ensureMenu(), because that would prevent my app from fully loading.

I'm not sure what to do exactly- if you have time to reach out to me, I am on https://gitter.im/aurelia/Discuss

The app does not start when using

activate(params) {
    return this.navigationMenu.ensureMenu()
  }

when I change it to

activate(params) {
   this.navigationMenu.ensureMenu()
  }

it works; however, I am not sure that will it work properly since the promise might not be resolved when activate method is done?

Any chance of including a a definition file into the plugin for those of us who use Typescript ?

I had two routes with named viewPorts, like so:

viewPorts: {
  main: {
    moduleId: PLATFORM.moduleName("x")
  },
  page: {
    moduleId: PLATFORM.moduleName("y")
   }
}

This caused a nullref on row 158 in https://github.com/jagonalez/aurelia-navigation-menu/blob/master/src/navigation-menu.js, since it is hardcoded to search for a viewPort called "default". Workaround was to rename one of the viewPorts.