Replies: 5 comments
-
UPD: It seems that parcel tries to be smart and remove "unused" variables from the code or something (hence, passing |
Beta Was this translation helpful? Give feedback.
-
Came across the exact same issue. Prod build works fine but dev is not working at expected |
Beta Was this translation helpful? Give feedback.
-
I tried to tweak the code around the error location, found that it looks like parcel mishandles the Try this workaround: Install import 'property-information'; // Just import
const Component = () => <ReactMarkdown>...</ReactMarkdown>; You can import before or after the react-markdown import, doesn't matter. Feel free to add |
Beta Was this translation helpful? Give feedback.
-
If this is still a problem, please open an issue with a complete reproduction. |
Beta Was this translation helpful? Give feedback.
-
It seems I incorporated this workaround a year ago, but upon visiting this part of the code today, it seems that I no longer need to import Currently installed: Don't know what has changed, but if anyone else who's tried this workaround want to report back, would love to know if the issue as fully gone away. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Original thread:
remarkjs/react-markdown#747
It seems that for whatever reason (see thread above) parcel does something weird in dev build so the
react-markdown
lib stops working when using links. Not sure what exactly triggers the issue, but prod build works fine..parcelrc
Beta Was this translation helpful? Give feedback.
All reactions