-
Notifications
You must be signed in to change notification settings - Fork 446
UglifyJs compile exception with @aspnet/signalr-client #867
Comments
@damienbod Just as an FYI, that can be simplified to:
The Uglify issue came up before here #729 (comment). It's an ES5 vs ES6 issue. |
@davidfowl This fix did not work. I replaced the lines here: This is where I do the Uglify configuration for the production build tried:
|
Looks like webpack.optimize.UglifyJsPlugin is not ready yet for this, so The SignalR lib cannot be uglified. |
This works if you use the new uglify packages, not the old. new packages => S is a capital letter... @FabianGosebrink thanks for your help. The fix: Step 1:in the package.json add: "uglifyjs-webpack-plugin": "1.0.0-beta.2", Step 2:add the UglifyJSPlugin webpack plugin (S is capital), in the webpack production build file const UglifyJSPlugin = require('uglifyjs-webpack-plugin'); Step 3:Update the webpack production build
|
This is because of Uglify not supporting ES6. See also #729 (which contains the same workaround you have) |
Lets put this in the known issues |
Done |
This might be fixed with angular/angular-cli#7610 - I will probably be checking this in the near future... |
What i did to get it working tsconfig.jason package,jason angular 4.4.4 |
The following 2 lines causes an UglifyJs compile exception:
UglifyJs Unexpected token: name (NullLogger)
https://dotnet.myget.org/feed/aspnetcore-ci-dev/package/npm/@aspnet/signalr-client
package version: 1.0.0-alpha1-26985
The text was updated successfully, but these errors were encountered: