Namespace 'Webpack' has no exported member 'Compiler'.

[HamedFathi]

I'm submitting a bug report

• Library Version:
  0.31.0

Please tell us about your environment:

• Operating System:
  Windows [7|10]

• Node Version:
  8.1.2

• NPM Version:
  5.0.3

• Browser:
  all

• Language:
  TypeScript 2.4.2

Current behavior:
I have problem when I call 'webpack' command.

Namespace 'Webpack' has no exported member 'Compiler'.
Namespace 'Webpack' has no exported member 'Options'.
Namespace 'Webpack' has no exported member 'Parser'.
Namespace 'Webpack' has no exported member 'Compilation'.
Namespace 'Webpack' has no exported member 'Resolver'.
Cannot find name 'DependencyOptionsEx'.
Invalid module name in augmentation. Module 'minimatch' resolves to an untyped module at C:/.../Desktop/aunew/autest/node_modules/minimatch/minimatch.js', which cannot be augmented.

[searus]

@HamedFathi I managed to fix this by adding an explicit reference to the webpack type definition in tsconfig.js:

  ...
  "exclude": [
    "node_modules",
    "aurelia_project"
  ],
  "files":[
    "./node_modules/@types/webpack/index.d.ts"
  ],
  "filesGlob": [
    "./src/**/*.ts",
    "./test/**/*.ts",
    "./custom_typings/**/*.d.ts"
  ],
  ...

Not sure if this is the correct fix, but it works for me.

[HamedFathi]

@searus

Yes it works, I added
"files":[
"./node_modules/@types/webpack/index.d.ts"
],

to tsconfig and works
I hope @EisenbergEffect fix it ASAP.

but now I have another problem

when I browse localhost:5000 I have the problem !

[JeroenVinke]

Sorry guys, seems to be related to aurelia/webpack-plugin#118. I'm looking into it now.

[JeroenVinke]

The fix mentioned by @searus (#700 (comment)) resolves the compiler issues for me.

@HamedFathi I've also tested this in an asp net core setup and after running dotnet run and going to localhost:5000 it works. Can you give me steps to reproduce? Thanks

[HamedFathi]

@JeroenVinke

1. I used latest CLI and choose SASS, WebPack, ASP.NET Core, VS Code
2. Update csproj with netcoreapp2.0
3. dotnet restore, dotnet build
4. add @searus `s tip to tsconfig
5. execute 'webpack' command
6. dotnet run

then

[shahabganji]

@HamedFathi and @JeroenVinke would take a look at the followings :

The src reference of index.html files do not match with what is generated in wwwroot of ASP.NET Core folder, they should refer to /dist/app.[hash].bundle.js and /dist/vendor.[hash].bundle.js
and in this case your url should also use the index.html file within the mentioned folder, the URL looks like : http://localhost:5000/dist/index.html
to eliminate such bad URLs you have to do some configs with ASP.NET Core, within its startup.cs file.( using app.UseStaticFiles() with options.

I don't have any idea why its still not using index.cshtml file and wants to download the hashed versions of the js files while in the index.cshtml file it referenced the app.js and vendor.js.

[JeroenVinke]

@shahabganji did you also upgrade to netcoreapp2.0? I don't seem to have issues with netcoreapp1.1. Still looking into it

[shahabganji]

@JeroenVinke Yes, I've updated to netcoreapp2.0

[JeroenVinke]

@HamedFathi @shahabganji I have a feeling that netcoreapp2.0 is more strict in how it expects the structure to be.

I don't have any idea why its still not using index.cshtml file and wants to download the hashed versions of the js files while in the index.cshtml file it referenced the app.js and vendor.js.

Yeah it should be using the Views, which it currently does not do. There are a couple of things that would have to change:

• webpack.config.js should not output files with hashes
• in asp.net core setup we don't need it to generate an index.html from index.ejs

This setup seems to be working (with netcoreapp2.0):
aurelia_project.zip

Getting these changes in and verifying that they don't break the non-asp.net setup will take some time. I'll open an issue