Angular-cli: beta-23: ngCompiler.ReflectorHost is not a constructor (again)

[drew-moore]

Please provide us with the following information:

OS?

Windows 10
Node 6.9.1
NPM 3.10.8

Versions.

1.0.0-beta.23

Repro steps.

ng new whatever
ng serve

The log given by the failure.

ngCompiler.ReflectorHost is not a constructor
TypeError: ngCompiler.ReflectorHost is not a constructor
at AotPlugin._setupOptions (C:\Users\moore\code\delme\node_modules\@ngtools\webpack\src\plugin.js:136:31)
at new AotPlugin (C:\Users\moore\code\delme\node_modules\@ngtools\webpack\src\plugin.js:37:14)
at Object.exports.getWebpackNonAotConfigPartial (C:\Users\moore\code\delme\node_modules\angular-cli\models\webpack-build-typescript.js:20:13)
at new NgCliWebpackConfig (C:\Users\moore\code\delme\node_modules\angular-cli\models\webpack-config.js:26:42)
at Class.run (C:\Users\moore\code\delme\node_modules\angular-cli\tasks\serve-webpack.js:20:22)
at C:\Users\moore\code\delme\node_modules\angular-cli\commands\serve.js:108:26
at process._tickCallback (internal/process/next_tick.js:103:7)`

Mention any other details that might be useful.

according to #3501, #3367, et. al. this is an angular 2.3.x incompatibility. #3569 made me assume this was resolved (2.3.1 was installed after re-running ng init), but apparently it hasn't. Downgrading angular to 2.2.x without downgrading cli results in: (also per #3569)

This version of CLI is only compatible with angular version 2.3.1 or better. Please upgrade your angular version, e.g. by running:

As such, my project cannot run with beta-23 at all and I'm having to downgrade.

[hansl]

Closing this as beta 23 is not released. Experimental builds are not released.

[drew-moore]

@hansl It's in the changelog and npm i [email protected] worked...

[hansl]

I unpublished it. The CHANGELOG is always a bit premature when a beta fails.

[jtsom]

And the point of making a new version, if we're not supposed to use it is what? And how do we know the difference between "experimental" beta and "not experimental" beta?

[drew-moore]

@jtsom we're supposed to use it once it's released, and "non-experimental" == released == published on npm. this one got published before it should've, but clearly that was just a mistake.

[jtsom]

Well, when it's under the "Releases" link of the repo, and when you click on it, it's label "Verified".. it looks like it should be a released version to me. I'm not knocking the "experimental" procedure, it just needs to be more clear. Given all the moving pieces that make up the ecosystem (Angular itself, the CLI, Typescript, and all their dependencies), it's difficult at best to make sure you are the right versions of everything. As of now, we can't even use the latest version of Angular with the "released" CLI - nevermind Typescript...

And how will we know when this "verified", "not released", "experimental" version is actually released and ready to use?

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}