I have updated my ionic project to angular 5 and i got the below error with many ionic native plugins..
angular/core/core"' has no exported member 'OpaqueToken
Resolved all of the issues after updating to the latest version , except for ionic-storage.
Still its giving this error
node_modules/#ionic/storage/es2015/storage.d.ts import { OpaqueToken }
from '#angular/core';
node_modules/#angular/core/core"' has no exported member 'OpaqueToken'.
We can see one open issue #github (142) but no fix or workaround found.
You can solve this issue by upgrading #ionic/storage to version 2.1.2 or higher.
Update (context):
OpaqueToken was removed in Angular v5 (it's been deprecated since
Angular v4). The corresponding change in the #ionic/storage package was done in this change as part of the 2.1.2 update.
Related
Dependencies could not be resolved because root depends on 'googleappmeasurement' 9.0.0.
'googleappmeasurement' 9.0.0 cannot be used because 'googleappmeasurement' 9.0.0 depends on 'nanopb' 2.30908.0..<2.30909.0 and root depends on 'nanopb' 2.30909.0..<2.30910.0.
that is my error message, can anyone help?
I am using SDK version 8.9.1 and everything working fine, If you executed the Resolve Package Versions and still not working. you can try the command Reset Package Caches from Project navigator scroll down right click on Package Dependencies then choose the command. that will clear all caches for all installed packages then re-install them again. if that not working i suggest you to use version 8.9.1 till Firebase fix the issue.
I have discovered the problem has been answered here. It occurs when importing Firebase using Swift Package Manager and setting to track "master" instead of a specific release version.
Got same error and solved, check attached image, this most likely packages usage misconfiguration, as follows:
1-perhaps you are working on a branch with different Xcode version than the other developer who installed the package.
2-Perhaps some package is conflicted being used twice, by so some dependencies are duplicated.
Well to solve this you gotta try either to match the Xcode version used while installing the packages, or to remove the package that makes errors(like Firebase here), and try adding that package again your side.
dears I am working on a flutter app where I need to add flutter_google_map V 4.0.0 and parse_server_sdk V 3.1.0 and each one depend on different version of http_package
the map depend on version 0.12.0
and parse_sdk depend on 0.13.3
there fore I am getting conflict issue
how I could resolved without done grade the versions
thanks in advance
try without versioning
flutter_google_map:
parse_server_sdk:
This is an error regarding ionic, I have just upgraded from IONIC 4 to IONIC 5. I have also upgraded my nodejs to latest version 12.16.4. Now I am getting error while performing ionic serve on my ionic projects. Could you please help me out in this regard?
There is a great tutorial video on the official Ionic YouTube channel which will show you a best-case scenario for upgrading to Ionic 5 and Angular 9.
However for my simple prototype app that I had made last year (just a demo that let me reorder a list) I tried to update but almost immediately came off the rails.
It turned out to be using "#angular/core": "^7.2.2" which broke the app from ionic serve because it was expecting Angular 8.
Then I tried to run the ng upgrade but got hit with incompatible peer dependencies for codelyzer, #ionic/angular-toolkit, and #angular/http.
So I tried to upgrade to Angular 8 first with npm i #angular/core#"~8.x.x" but that failed as it needed npm i zone.js#~0.9.1.
How can I update successfully to the latest and greatest?
So for people coming from angular 7 it seems for this project the correct upgrade commands are:
npm i #ionic/angular#latest
npm i zone.js#~0.9.1
npm i #angular/core#"~8.x.x"
npm i #ionic/angular-toolkit#latest
npm i codelyzer#latest
npm remove #angular/http
ng update #angular/core #angular/cli --allow-dirty
and it finally updated everything. However I did see a warning saying Package not installed: "--allow-dirty". Skipping.
However, then after that I dared to try ionic build and it failed with this error, which got me stuck for another 15 minutes:
zone-flags.ts is missing from the TypeScript compilation.
It seems that the polyfills.ts uses the .ts extension in the include which is breaking the compilation.
I changed this line in polyfills.ts:
import './zone-flags.ts';
To this:
import './zone-flags';
AND IT COMPILED.
But did it ionic serve?
No. No it did not.
The browser showed this in the console:
Error: Angular JIT compilation failed: '#angular/compiler' not loaded!
So after some more searching, I found that if you open main.ts and then add
import '#angular/compiler';
Near the top then all will be right and good with the world once more...
...unless your project then needs the markup breaking changes resolving, but you're on your own for that.
I have migrated to the upcoming version (v1) of material-UI, and I installed v1 alongside the current version according to the recommendation:
yarn add material-ui#latest
yarn add material-ui-next#npm:material-ui#next
When I try to use redux-form and use the package redux-form-material-ui to connect the components, it searches for the material-UI components in "material-ui" folder, which gives an error:
Error: Can't resolve 'material-ui/Radio' in 'C:\path\to\redux-form-material-ui\lib'
But I import Radio from material-ui-next/Radio
So it looks for it in the wrong version.
How can I make this work? Should I uninstall the current version and install "next" as "material-ui" instead?
Here is what is installed:
"material-ui": "^0.20.0",
"material-ui-next": "npm:material-ui#next",
"redux-form-material-ui": "^5.0.0-beta.2",
"redux-form": "^7.3.0",
My way of getting around the problem was to uninstall both material UI packages and then install the v1 as "material-ui" , and the old one as "material-ui-old":
"material-ui": "npm:material-ui#next",
"material-ui-old": "npm:material-ui"
I had to change all the imports in the project.
But now it finds the 'material-ui/Radio'.