Corrupted published package - export 'ReactNativeZoomableViewProps' was not found in './typings'
Closed this issue · 5 comments
We are using this package in Expo with react-native-web. There is no issue in native application, but web displays following warnings right after build and also in a browser console:
./node_modules/@openspacelabs/react-native-zoomable-view/lib/module/index.js:4
"export 'ReactNativeZoomableViewProps' was not found in './typings'
2 | import ReactNativeZoomableViewWithGestures from './ReactNativeZoomableViewWithGestures';
3 | import { ReactNativeZoomableViewProps, ZoomableViewEvent } from './typings';
> 4 | export { ReactNativeZoomableView, ReactNativeZoomableViewWithGestures, ReactNativeZoomableViewProps, ZoomableViewEvent };
5 | //# sourceMappingURL=index.js.map
6 |
./node_modules/@openspacelabs/react-native-zoomable-view/lib/module/index.js:4
"export 'ZoomableViewEvent' was not found in './typings'
2 | import ReactNativeZoomableViewWithGestures from './ReactNativeZoomableViewWithGestures';
3 | import { ReactNativeZoomableViewProps, ZoomableViewEvent } from './typings';
> 4 | export { ReactNativeZoomableView, ReactNativeZoomableViewWithGestures, ReactNativeZoomableViewProps, ZoomableViewEvent };
I think that problem is somewhere in a build process, where exports of interfaces were not removed from built .js files properly.
When I try to comment out the problematic exports in ./node_modules/@openspacelabs/react-native-zoomable-view/lib/module/index.js, the warnings will disappear.
// File ./node_modules/@openspacelabs/react-native-zoomable-view/lib/module/index.js
import ReactNativeZoomableView from './ReactNativeZoomableView';
import ReactNativeZoomableViewWithGestures from './ReactNativeZoomableViewWithGestures';
// import { ReactNativeZoomableViewProps, ZoomableViewEvent } from './typings';
export { ReactNativeZoomableView, ReactNativeZoomableViewWithGestures /*, ReactNativeZoomableViewProps, ZoomableViewEvent*/ };
//# sourceMappingURL=index.js.map
same here, version "^2.0.4"
still no solution
Same issue, fix mentioned here works! Created a patch in my project to move forward. Hope this gets fixed soon.
When will this be fixed?
@ibovegar @mgroeneweg @antonkristiono @linojon
Sorry for the delay. I've created #65 which I think will fix this by fixing the import syntax. Could you please try it and let me know?
Side note – PRs are always welcome and the best way to help!