Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for Web
See original GitHub issueI get bug reports from people using this library and trying to run their apps on the web using React Native for Web.
Web support could be added by exporting the SVG components from React DOM or wrapping them in React Native for Web’s createElement. And compiling the package before publishing to npm. It may be complicated by the decision to deviate from the SVG standard and add things like setNativeProps to the native components.
Here’s an example of how much massaging needs to be done to convert this library’s API to the SVG standard on web https://github.com/godaddy/svgs/blob/master/index.js
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:34
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hmm, is https://github.com/godaddy/svgs insufficient?
I’ve forked svgs to support react-native-web and published it under the name swgs to see how much interest there is for this https://www.npmjs.com/package/swgs Essentially the only difference so far is to use
import { createElement } from 'react-native-web';instead ofimport React from 'react';https://github.com/msand/swgs/commit/d5ac0a4e93e6bad3b8ed190c6833adf58361fcfc#diff-168726dbe96b3ce427e7fedce31bb0bcR1 @necolas Are there any more changes needed on the native side or in swgs at this point?