ngx-datatable: Build failed due to 'Metadata version mismatch' in 11.0.0

AoT build failed Error: Metadata version mismatch for module ~/node_modules/@swimlane/ngx-datatable/release/datatable.module.d.ts, found version 4, expected 3

I’m submitting a BUG (check one with “x”)

[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

Error: Metadata version mismatch for module ~/node_modules/@swimlane/ngx-datatable/release/datatable.module.d.ts, found version 4, expected 3

after upgrade 11.0.0 Expected behavior

Reproduction of the problem

What is the motivation / use case for changing the behavior?

npm build to AoT Please tell us about your environment:

macOS 12.13.1 npm

Table version: 0.8.x

Angular version: 2.0.x

4.6.6

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

all

Language: [all | TypeScript X.X | ES6/7 | ES5] ES6

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 3
Comments: 21 (5 by maintainers)

Most upvoted comments

Same error here. but fixed with “@swimlane/ngx-datatable”: “10.4.0”
I removed “^” before 10.4.0

knehez on Nov 8, 2017

The same issue: ERROR in Metadata version mismatch for module …/node_modules/@swimlane/ngx-datatable/release/index.d.ts, found version 4, expected 3, version: 10.0.5 Angular: 4.3.5 cli: 1.3.0 node: v7.7.3 npm: 4.1.2

pr0menade on Nov 6, 2017

@nitinht1988 I’m having the same issue with version 10.5.0 and Angular 4.4.6.

EDIT: It shows the error, but works though.

mattarau on Nov 6, 2017

I have the same problem and i’ve not yet solved it. I cant continue my job cause of this problem…waiting for help.

ERROR in Metadata version mismatch for module node_modules/@swimlane/ngx-datatable/release/index.d.ts, found version 4, expected 3

Datatable version: 10.5.0 Angular: 4.4.6 Cli: 1.3.2 Node: 8.9.0 Npm: 5.3.0

Neuropatic on Nov 7, 2017

I can confirm the issue, using Angular 4. And I can also confirm that the solution posted by @knehez works. So my guess is that there is something wrong with version 10.5.0.

FrancescoBorzi on Nov 13, 2017