It was my first time using Mappedin and I am integrate it via @mappedin/react-sdk. Currently, it’s working fine for runtime but my compiler got error message when I passed mapData from useMapData with credentials to component:
”TS2719: Type MapData is not assignable to type MapData. Two different types with this name exist, but they are unrelated. Property #private in type MapData refers to a different member that cannot be accessed from within type MapData”
Could anyone guide me what I have done anything wrong with my implementation?
Check that the @mappedin/react-sdk and @mappedin/mappedin-js used in your project are the same version. Currently there are breaking changes between our beta and rc (release candidate) releases. We will be releasing a rc version of @mappedin/react-sdk that will align it with Mappedin JS rc next week.
Ohh Hi @msohm , thanks for your response. Currently I only installed @mappedin/react-sdk because as the documentation said only install one of those 2 packages.
When using @mappedin/react-sdk, do not install or import @mappedin/mappedin-js. The Mappedin SDK for React includes Mappedin JS. Including both can cause build conflicts or runtime errors due to duplicated or mismatched dependencies.
My current version is 6.0.1-beta.54.
In conclusion, we have to wait for the next release right?
You have done it correctly. Please try downgrading to 6.0.1-beta53. There have been some conflicts that came up in beta-54. That may resolve the issue for you now, if not then yes, you’ll need to wait for the RC build which is coming very soon.
We have released Mappedin SDK for React v6.0.0-rc.2, which resolves these issues. Note that you now do need to add both @mappedin/react-sdk and @mappedin/mappedin-js to your project. The same versions of each should be used to ensure compatibility.
The RC builds do have some breaking changes from the beta releases. These are details in the Release Notes.