我在 beta-11 级别使用 Angular Material 2 进行了一个干净的新项目。这引入了围绕材质控件和样式使用 mat - 前缀而不是 md - 前缀的重大变化。
我没有MaterialJS控件，也没有使用任何材质样式。这只是一个非常简单的Material测试，在我的HTML中只有一个<mat-card></mat-card>。
该项目在运行时失败并显示错误，告诉我我在兼容模式下运行（为什么？我没有要求？我不想！）所以mat-prefix可以＆＃ 39;不能使用。
我可以通过在我的根模块中导入AngularJS兼容模式模块（ NoConflictStyleCompatibilityMode ）来删除错误并运行OK，但为什么我需要这样做，因为这是一个新的空白项目，没有需要兼容性吗？
如果我没有为我非常简单的＆＃34; beta 11＆＃34;导入兼容模式模块，这就是我得到的错误。测试项目。
**Uncaught (in promise): Error: The "mat-" prefix cannot be used in ng-material v1 compatibility mode. It was used on an "mat-card" element.
Error: The "mat-" prefix cannot be used in ng-material v1 compatibility mode. It was used on an "mat-card" element.
at getMdCompatibilityInvalidPrefixError (core.es5.js:55)
at new MatPrefixRejector (core.es5.js:76)
at createClass (core.es5.js:10936)
at createDirectiveInstance (core.es5.js:10764)
at createViewNodes (core.es5.js:12212)
at callViewAction (core.es5.js:12661)
at execComponentViewsAction (core.es5.js:12570)
at createViewNodes (core.es5.js:12239)
at createRootView (core.es5.js:12107)
at callWithDebugContext (core.es5.js:13493)
at getMdCompatibilityInvalidPrefixError (core.es5.js:55)
at new MatPrefixRejector (core.es5.js:76)
at createClass (core.es5.js:10936)
at createDirectiveInstance (core.es5.js:10764)
at createViewNodes (core.es5.js:12212)
at callViewAction (core.es5.js:12661)
at execComponentViewsAction (core.es5.js:12570)
at createViewNodes (core.es5.js:12239)
at createRootView (core.es5.js:12107)
at callWithDebugContext (core.es5.js:13493)
at resolvePromise (zone.js:824)
at resolvePromise (zone.js:795)
at zone.js:873
at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:425)
at Object.onInvokeTask (core.es5.js:3881)
at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:424)
at Zone.webpackJsonp.../../../../zone.js/dist/zone.js.Zone.runTask (zone.js:192)
at drainMicroTaskQueue (zone.js:602)
at <anonymous>
defaultErrorLogger @ core.es5.js:1020
webpackJsonp.../../../core/@angular/core.es5.js.ErrorHandler.handleError @ core.es5.js:1080
next @ core.es5.js:4503
schedulerFn @ core.es5.js:3635
webpackJsonp.../../../../rxjs/Subscriber.js.SafeSubscriber.__tryOrUnsub @ Subscriber.js:238
webpackJsonp.../../../../rxjs/Subscriber.js.SafeSubscriber.next @ Subscriber.js:185
webpackJsonp.../../../../rxjs/Subscriber.js.Subscriber._next @ Subscriber.js:125
webpackJsonp.../../../../rxjs/Subscriber.js.Subscriber.next @ Subscriber.js:89
webpackJsonp.../../../../rxjs/Subject.js.Subject.next @ Subject.js:55
webpackJsonp.../../../core/@angular/core.es5.js.EventEmitter.emit @ core.es5.js:3621
(anonymous) @ core.es5.js:3912
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invoke @ zone.js:392
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.run @ zone.js:142
webpackJsonp.../../../core/@angular/core.es5.js.NgZone.runOutsideAngular @ core.es5.js:3844
onHandleError @ core.es5.js:3912
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.handleError @ zone.js:396
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.runGuarded @ zone.js:158
_loop_1 @ zone.js:702
api.microtaskDrainDone @ zone.js:711
drainMicroTaskQueue @ zone.js:610
Promise resolved (async)
scheduleMicroTask @ zone.js:585
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.scheduleTask @ zone.js:414
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.scheduleTask @ zone.js:236
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.scheduleMicroTask @ zone.js:256
scheduleResolveOrReject @ zone.js:871
ZoneAwarePromise.then @ zone.js:981
webpackJsonp.../../../core/@angular/core.es5.js.PlatformRef_._bootstrapModuleWithZone @ core.es5.js:4537
webpackJsonp.../../../core/@angular/core.es5.js.PlatformRef_.bootstrapModule @ core.es5.js:4522
../../../../../src/main.ts @ main.ts:11
__webpack_require__ @ bootstrap e863d796c3f68ad142cb:54
0 @ main.bundle.js:391
__webpack_require__ @ bootstrap e863d796c3f68ad142cb:54
webpackJsonpCallback @ bootstrap e863d796c3f68ad142cb:25
(anonymous) @ main.bundle.js:1**