These are chat archives for AngularClass/angular2-webpack-starter

22nd
Nov 2016
Brian Thompson
@brianrt
Nov 22 2016 14:00
@ChrisGrant Well, I don'
Don't know exactly what it means but the A2 CI build for IE9 is failing (https://saucelabs.com/u/angular2-ci)
Brian Thompson
@brianrt
Nov 22 2016 14:09
There's no closes or open issues with this exact error, so perhaps you put in a ticket on the A2 github.
Since that seems more action that the gitter
Active*
Chris Grant
@ChrisGrant
Nov 22 2016 15:16
@Nocomm hmm yeah so it is. Thanks! I will keep digging around to find out more and consider opening an issue.
Brian Thompson
@brianrt
Nov 22 2016 15:17
No prob. I wish I could provide more help :smile:
zwang60
@zwang60
Nov 22 2016 16:54
Hi all. does anyone had an error like this when running npm start?
when I run npm start, there's a error
C:\Users\Documents\project\node_modules\webpack-dev-server\lib\Server.js:23
var validationErrors = webpack.validateSchema(optionsSchema, options);
^
TypeError: webpack.validateSchema is not a function
at new Server (C:\Users\Documents\project\node_modules\webpack-dev-server\lib\Server.js:23:33)
at startDevServer (C:\Users\Documents\project\node_modules\webpack-dev-server\bin\webpack-dev-server.js:369:12)
at processOptions (C:\Users\Documents\project\node_modules\webpack-dev-server\bin\webpack-dev-server.js:307:3)
at Object.<anonymous> (C:\Users\Documents\project\node_modules\webpack-dev-server\bin\webpack-dev-server.js:431:1)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.runMain (module.js:590:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
Brian Thompson
@brianrt
Nov 22 2016 17:00
check your node_modules directory to see if webpack is even installed
or do ./node_modules/.bin/webpack --v
zwang60
@zwang60
Nov 22 2016 17:03
yeah
$ ./node_modules/.bin/webpack --v
Hash: de7c6102c2cf2ebb63ac
Version: webpack 2.1.0-beta.22
Brian Thompson
@brianrt
Nov 22 2016 17:05
Hmmm... I'm on beta 27. Honestly never seen that error. But what it means is that the webpack-dev-server can't find webpack. Webpack works fine though?
zwang60
@zwang60
Nov 22 2016 17:06
webpack was working, but now it's probably not
so do you recommend me upgrade to beta 27, would that help?
Brian Thompson
@brianrt
Nov 22 2016 17:07
Might help. webpack-dev-server 2.1.0-beta.11 and webpack 2.1.0-beta.27
zwang60
@zwang60
Nov 22 2016 17:19
okay, that works! but after this problem solved, it comes up with another problem
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
  • configuration has an unknown property 'tslint'. These properties are valid:
    object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
    For typos: please correct them.
    For loader options: webpack 2 no longer allows custom properties in configuration.
    Loaders should be updated to allow passing options via loader options in module.rules.
    Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
    plugins: [
    new webpack.LoaderOptionsPlugin({
      // test: /\.xxx$/, // may apply this only for some modules
      options: {
        tslint: ...
      }
    })
    ]
  • configuration.module has an unknown property 'postLoaders'. These properties are valid:
    object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp? }
    Options affecting the normal modules (NormalModuleFactory).
  • configuration.node.global should be a boolean.
  • configuration.resolve.extensions[0] should not be empty.
Brian Thompson
@brianrt
Nov 22 2016 17:21
Sounds like a missing plugin. "npm install tslint tslint-loader"
"npm install tslint tslint-loader --save-dev"
They should already come with the package though...
And by package I mean project.
zwang60
@zwang60
Nov 22 2016 17:25
okay, while after run this command, the problem still exist
Brian Thompson
@brianrt
Nov 22 2016 17:45
Ah... you're using an older version of the project. I gave the newest project's versions of webpack and its dev server which doesn't support tslint in the configuration out of the box (not sure if it ever did, but it used to in the project).
zwang60
@zwang60
Nov 22 2016 17:55
yeah, I am using webpack-starter version 5.0.5
cant
@cantux
Nov 22 2016 19:12
Hello, first timer, so please point out if there is a guideline on posting here
/How would I go about debugging using Webstorm 2016.3? Thanks
cant
@cantux
Nov 22 2016 19:34
here is the output of webstorm debug when I tried to add an "npm" debug configuration: https://gist.github.com/cantux/65e89e953336ba7666ca3f483060ff58