Testing Ionic 4 - Cannot find type definition file for 'cordova'
See original GitHub issueDescription:
Steps to Reproduce: Delete node-modules Upgrade to 4.0.0-alpha.4 npm i
Output:
C:\Users\peter>cd C:\ae\adaept.com\aemenu
C:\ae\adaept.com\aemenu>npm i
> node-sass@4.9.0 install C:\ae\adaept.com\aemenu\node_modules\node-sass
> node scripts/install.js
Cached binary found at C:\Users\peter\AppData\Roaming\npm-cache\node-sass\4.9.0\win32-x64-57_binding.node
> node-sass@4.9.0 postinstall C:\ae\adaept.com\aemenu\node_modules\node-sass
> node scripts/build.js
Binary found at C:\ae\adaept.com\aemenu\node_modules\node-sass\vendor\win32-x64-57\binding.node
Testing binary
Binary is fine
> @angular/cli@6.0.0 postinstall C:\ae\adaept.com\aemenu\node_modules\@angular\cli
> node ./bin/ng-update-message.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.3 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
added 1087 packages from 1271 contributors in 46.066s
C:\ae\adaept.com\aemenu>ionic s
> ng serve --host=0.0.0.0 --port=8100
[INFO] Development server running!
Local: http://localhost:8100
External: http://192.168.1.67:8100
DevApp: aemenu@8100 on Merry-Christmas
[INFO] Browser window opened to http://localhost:8100!
[ng] i 「wdm」: wait until bundle finished: /
[ng] Date: 2018-05-10T05:34:35.695Z
[ng] Hash: 742c44f0cc752f330449
[ng] Time: 9526ms
[ng] chunk {main} main.js, main.js.map (main) 1.9 kB [initial] [rendered]
[ng] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 669 bytes [initial] [rendered]
[ng] chunk {runtime} runtime.js, runtime.js.map (runtime) 5.4 kB [entry] [rendered]
[ng] chunk {styles} styles.js, styles.js.map (styles) 20.1 kB [initial] [rendered]
[ng] chunk {vendor} vendor.js, vendor.js.map (vendor) 325 kB [initial] [rendered]
[ng]
[ng] ERROR in node_modules/@ionic-native/core/decorators/common.d.ts(1,23): error TS2688: Cannot find type definition file for 'cordova'.
[ng]
[ng] i 「wdm」: Failed to compile.
My ionic info
:
C:\ae\adaept.com\aemenu>ionic info
cli packages: (C:\Users\peter\AppData\Roaming\npm\node_modules)
@ionic/cli-utils : 2.0.0-rc.6
ionic (Ionic CLI) : 4.0.0-rc.6
global packages:
cordova (Cordova CLI) : 8.0.0
local packages:
@angular-devkit/core : 0.6.0
@angular-devkit/schematics : 0.6.0
@angular/cli : 6.0.0
@ionic/schematics-angular : 1.0.0-rc.6
Cordova Platforms : none
Ionic Framework : @ionic/angular 4.0.0-alpha.4
System:
NodeJS : v8.11.1
npm : 6.0.0
OS : Windows 10
Environment Variables:
ANDROID_HOME : not set
C:\ae\adaept.com\aemenu>
Other Information:
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Cannot find type definition file for 'cordova' : diagnostic plugin
I am unable to build my ionic 3 project ...
Read more >Cannot find type definition file for '@types' - Ionic Forum
Hi,. I am trying to build my app with the --prod flag. ionic cordova build android --verbose --prod. However, when I do, I...
Read more >Cannot find type definition file for 'node' in TypeScript
To solve the error "Cannot find type definition file for node", install the node types by running npm i -D @types/node . If...
Read more >Blog - Apache Cordova
For Android, the RECORD_VIDEO permission definition was removed as it was never used and appears to never exist. The cordova-plugin-file ...
Read more >cordova-plugin-firebasex - npm
Download your Firebase configuration files, GoogleService-Info.plist for iOS and google-services.json for android, and place them in the root ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Deleting the node_modules folder and the package-lock.json and then a clean npm install fixed the problem. Seems just to be some kind of minor update dependency problem. Nothing to worry about. Thanx for pointing this out, @dwieeb .
I will do it this evening when I am on that machine again.