TypeError: customConfig.configure is not a function #2

Zensavona · 2016-03-17T05:04:46Z

Hi guys,

I've come across an issue while using this bootstrapper, here's the error I'm getting in the browser console while running with npm run dev:

TypeError: customConfig.configure is not a function
    at eval (webpack:///./~/aurelia-bootstrapper-webpack/dist/commonjs/aurelia-bootstrapper-webpack.js?:60:27)

I did a bit of digging and found that on line 58-60 of aurelia-bootstrapper-webpack/dist/commonjs/aurelia-bootstrapper-webpack.js exists the following code. I did a bit of console.logging and I've added some comments indicating the values being passed into here which produce this error.

  // configModuleId === 'main'
  return loader.loadModule(configModuleId).then(function (customConfig) {
      // customConfig === {}
      return customConfig.configure(aurelia);
    });

Why this is happening, I'm not exactly sure, but my main.js looks like this:

import {bootstrap} from 'aurelia-bootstrapper-webpack';

import '../node_modules/bootstrap/dist/css/bootstrap.css';
import '../node_modules/font-awesome/css/font-awesome.css';
import '../assets/css/style.css';

bootstrap(function(aurelia) {
  aurelia.use
    .standardConfiguration()
    .developmentLogging()
    .plugin('aurelia-validation')
    .plugin('aurelia-dialog')
    .plugin('aurelia-flux')
    .feature('resources');

  aurelia.start().then(() => aurelia.setRoot('app', document.body));
});

I can strip it back to the following and still reproduce the error:

import {bootstrap} from 'aurelia-bootstrapper-webpack';

import '../node_modules/bootstrap/dist/css/bootstrap.css';
import '../node_modules/font-awesome/css/font-awesome.css';
import '../assets/css/style.css';

bootstrap(function(aurelia) {
  aurelia.use
    .standardConfiguration()
    .developmentLogging();

  aurelia.start().then(() => aurelia.setRoot('app', document.body));
});

Any ideas?

The text was updated successfully, but these errors were encountered:

Vheissu · 2016-03-23T02:54:39Z

I am experiencing the same issue as you. I am using the enhance feature and thought this was the reason. Evidently not. The fix I found was to add in a simple check to see if the configure method exists. When I put a breakpoint in, I can see it is trying to call configure on an empty object {}

Vheissu · 2016-03-23T03:00:43Z

Try this PR: #4 - it fixes the issue for me.

Vheissu · 2016-03-23T04:03:36Z

@Zensavona After speaking with @EisenbergEffect this appears to be a misunderstanding of the difference between Webpack and the standard Skeleton. If you use Webpack, you don't need an aurelia-app="main" attribute as you specify the main entry point inside of your Webpack configuration. After removing the aurelia-app attribute, the issue went away.

Vheissu · 2016-04-05T02:14:25Z

@EisenbergEffect This can be closed.

veikkoeeva · 2016-08-28T14:05:02Z

It looks like the WebPack skeletons at https://github.com/aurelia/skeleton-navigation/blob/master/skeleton-typescript-webpack/index.html have <body aurelia-app="main"> defined. It looks like I'm running to this problem in my little demo at https://github.com/veikkoeeva/AureliaDemo/tree/master/src/AureliaDemo.FrontEnd and I'm a tad loss what would be the right configuration.

niieani · 2016-08-28T16:04:01Z

@veikkoeeva Yeah, the new skeletons don't need you to use the bootstrapper manually, it works with the aurelia-app just as the JSPM skeletons.

Sigfried · 2016-10-06T10:46:00Z

I have no idea what I'm doing (first attempt using aurelia), but I'm getting this same error message. I'm trying to use https://github.com/code-chris/aurelia-knockout with a new aurelia-cli project. The instructions with aurelia-knockout are not clear to me, but this is what I'm trying:

I cp -r .../aurelia-knockout/dist/es2015 into .../src/aurelia-knockout in my new app. Then (with au run --watch) I get Error: ENOENT: no such file or directory, open .../src/knockout.js. So then I put a copy of knockout.min.js in .../src, and then au run doesn't complain anymore, but the browser console gives me the vendor-bundle.js:3394 TypeError: customConfig.configure is not a function error.

I can log this as an issue with aurelia-knockout, but I ended up here first from googling the error message.

EisenbergEffect · 2016-10-06T14:13:21Z

I would definitely ask a question on the aurelia-knockout plugin Github. I'm not sure how they put that plugin together. How they did that would probably affect your app's configuration. I can tell you that knockout shouldn't go in the src folder. Instead, put in in scripts or use npm to install it. In your CLI app's aurelia.json file you will need to add it as a dependency so you can map the name knockout to the knockout.min.js file.

digitalheir · 2016-11-15T21:41:31Z

I don't understand why this issue is closed?

skeleton-esnext-webpack still gives this error out of the box and provides a poor onboarding experience for Aurelia + webpack. The one with Gulp does work.

EisenbergEffect · 2016-11-15T21:59:10Z

@niieani Can you comment on this? Is this a breaking change in Weback's code again?

digitalheir · 2016-11-16T10:52:09Z

Oops, I'm in the wrong repo. My issue was with the navigation skeleton release at https://github.com/aurelia/skeleton-navigation/releases/tag/1.1.1 . I think this is the one. Excuse me.

niieani · 2016-11-16T13:11:32Z

@EisenbergEffect yeah, it's breaking change in Webpack, basically we need to lock the webpack-dev-server too (we only locked 'webpack' before). We discussed it with @Vheissu already.

EisenbergEffect · 2016-11-16T13:56:59Z

Is that in a PR?

niieani · 2016-11-16T14:03:48Z

I'll adjust the PR to use locked webpack versions so we don't get these sort of problems in the future. But I'm working on a fix for old skeletons now.

EisenbergEffect · 2016-11-16T14:04:32Z

Cool. Thanks!

niieani · 2016-11-16T14:11:27Z

Fixes pushed to master aurelia/skeleton-navigation@cb30c75.

Vheissu mentioned this issue Mar 23, 2016

fix(all): issue with configure method on empty object fixed #4

Closed

EisenbergEffect closed this Apr 5, 2016

Sigfried mentioned this issue Oct 6, 2016

TypeError: customConfig.configure is not a function aurelia-contrib/aurelia-knockout#6

Closed

SteveSandersonMS mentioned this issue Oct 24, 2016

Add AureliaSpa template aspnet/JavaScriptServices#398

Closed

aurelia / bootstrapper-webpack

TypeError: customConfig.configure is not a function #2

TypeError: customConfig.configure is not a function #2

Zensavona commented Mar 17, 2016

Vheissu commented Mar 23, 2016

Vheissu commented Mar 23, 2016

Vheissu commented Mar 23, 2016

Vheissu commented Apr 5, 2016

veikkoeeva commented Aug 28, 2016

niieani commented Aug 28, 2016

Sigfried commented Oct 6, 2016

EisenbergEffect commented Oct 6, 2016

digitalheir commented Nov 15, 2016 •

edited

EisenbergEffect commented Nov 15, 2016

digitalheir commented Nov 16, 2016 •

edited

niieani commented Nov 16, 2016 •

edited

EisenbergEffect commented Nov 16, 2016

niieani commented Nov 16, 2016

EisenbergEffect commented Nov 16, 2016

niieani commented Nov 16, 2016

aurelia / bootstrapper-webpack

Sponsor aurelia/bootstrapper-webpack

TypeError: customConfig.configure is not a function #2

TypeError: customConfig.configure is not a function #2

Comments

Zensavona commented Mar 17, 2016

Vheissu commented Mar 23, 2016

Vheissu commented Mar 23, 2016

Vheissu commented Mar 23, 2016

Vheissu commented Apr 5, 2016

veikkoeeva commented Aug 28, 2016

niieani commented Aug 28, 2016

Sigfried commented Oct 6, 2016

EisenbergEffect commented Oct 6, 2016

digitalheir commented Nov 15, 2016 • edited

EisenbergEffect commented Nov 15, 2016

digitalheir commented Nov 16, 2016 • edited

niieani commented Nov 16, 2016 • edited

EisenbergEffect commented Nov 16, 2016

niieani commented Nov 16, 2016

EisenbergEffect commented Nov 16, 2016

niieani commented Nov 16, 2016

digitalheir commented Nov 15, 2016 •

edited

digitalheir commented Nov 16, 2016 •

edited

niieani commented Nov 16, 2016 •

edited