Sorry @beatsm. This is due to two breaking changes introduced in dependencies: one in Webpack (as mentioned by @nil4); the other in TypeScript. I'll try to publish an updated Yeoman generator today that fixes both, but in the meantime, you can fix your project like this:

Run yo aspnetcore-spa to create your Aurelia app. Compilation will fail with the not a loader message.
Edit your newly-generated package.json file to lock on to Webpack 2.1.0-beta.25 exactly (rather than allowing newer betas), since that's the only version compatible with Aurelia's webpack loader at the moment. So, edit line 42 so instead of saying "^2.1.0-beta.25", it says "2.1.0-beta.25" (i.e., remove the ^ character).
Back in your command prompt, run npm install again to make your change take effect
Also edit ClientApp/app/components/fetchdata/fetchdata.ts, changing line 16 from this.forecasts = data; to this.forecasts = data as any;.

Now things will build and run as expected. Run webpack --config webpack.config.vendor.js to rebuild your vendor files, then webpack to rebuild your app files, then dotnet run.

Aurelia template error #469

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions