modules[moduleId].call breaks aurelia-testing about loader-webpack HOT 27 CLOSED

New release coming up in few days (~ 5 - 15).
aurelia/skeleton-navigation#714.

from loader-webpack.

I hate to bring this up again, but as I mentioned in the above ticket three weeks ago, this issue is blocking me from updating to the ^1.0.0 release of Aurelia with webpack.

Is there is an update, quick fix or workaround for this issue, I would be very appreciative.

from loader-webpack.

You could try using the older, [email protected] instead of 1.0.3. It might work, but might also introduce other bugs. Otherwise, the fix should land sometime in November.

from loader-webpack.

This problem appears to affect ES6 code also - not just TS. See:

aurelia/testing#40

Effectively blocking all testing of viewmodels, custom elements, etc.

from loader-webpack.

Yes, it's not written anywhere that it's TS specific. It's not related to the language.

from loader-webpack.

I might be having the same issue. WebpackLoader.loadModule fails with Unhandled rejection Error: Loading chunk 0 failed.

Snippets of relevant code looks like:

import {configure} from '../shared/validation';
import {$beforeEach} from 'async-await-jasmine';
import {bootstrap} from 'aurelia-bootstrapper-webpack';
import {ComponentTester, StageComponent} from 'aurelia-testing';

  $beforeEach(async () => {
    component = StageComponent
      .withResources('subjects/add-new-subject')
      .inView('<add-new-subject></add-new-subject>')
      .boundTo({});
    component.bootstrap(configure);
    await component.create(<any> bootstrap);
});

import {Aurelia} from 'aurelia-framework';
import {DOM} from 'aurelia-pal';

export function configure(aurelia: Aurelia) {
  'use strict';

  aurelia.use
    .standardConfiguration()
    .plugin('aurelia-validation');
}

from loader-webpack.

We have a very large BI application that is being written using Aurelia. This issue is effectively blocking all unit testing for UI components.

from loader-webpack.

I will be tackling this in the next week or two.

from loader-webpack.

Any update on this? Sorry to hassle you.

from loader-webpack.

@stevies It's almost ready, but something got in the way of me finishing it. Give it a few more days.

from loader-webpack.

Does your work on the new experimental skeleton mean that you now have no plans to fix this defect?

from loader-webpack.

@stevies the new Webpack plugins which are used by the nee skeleton is the fix for this defect. Aurelia Webpack Plugin, which is the culprit here, will be deprecated, but migration to the new set of Webpack plugins will be straight forward and very easy. For those using easy-webpack I'll simply create a major version bump on @easy-webpack/config-aurelia which contains all the changes.

from loader-webpack.

Cool. I'll wait on the new stuff being released.

from loader-webpack.

Any updates? I'm probably going to have to look at switching to using something other than Webpack in the short to medium term. Last time I looked at the CLI for building it was horrible to use, but I might have to live with that since not being able to test anything is a real problem.

from loader-webpack.

Its 2017, any update on this?

from loader-webpack.

Hey guys, I'm sorry I couldn't meet the deadline I've set for myself. The remaining workload isn't overwhelming, but I'm struggling to find time to work on it since December. We might be getting a new team member soon, so hopefully, if not by me, this should be resolved relatively soon.

from loader-webpack.

Bump.

from loader-webpack.

New release coming up in few days (~ 5 - 15).

Sorry to bother you about it @niieani but, any news about that?

from loader-webpack.

Sorry @lukefx, been working on it, on and off, as I've been busy and now I'm a bit ill too, which doesn't help.

from loader-webpack.

Came across the issue here as well. Is there any way we can help to speed along the fix? (Currently using the @easy-webpack from the skeletons)

from loader-webpack.

Same issue here. Just pinging.

from loader-webpack.

Fixed by aurelia/skeleton-navigation#714

from loader-webpack.

I still get errors with the new skeleton for tests that uses StageComponent in the browser.

Can someone else confirms whether StageComponent tests compiled by webpack and run in the browser (not jest) are working ok or not?

from loader-webpack.

@nashwaan They are not working for me.

from loader-webpack.

@niieani Can you reopen this issue?

from loader-webpack.

aurelia/testing#21 is also similar, and currently open, though not labeled as a bug.

from loader-webpack.

I just like to confirm the updated skeleton has solved the issue related to asynchronous StageComponent.

Thanks for your efforts @niieani .
😊

from loader-webpack.