You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been studying the source code of this project recently, and my understanding is that the core function of vite-plugin-md is to convert Markdown files into Vue Single File Components (SFCs) during the build phase.
However, I see a use case where we might want to dynamically convert user input Markdown text into Vue components at runtime, which would require performing the Markdown to Vue component conversion on the client side. In other words, the conversion logic needs to be moved to the browser: I am contemplating porting the core logic of this project (i.e., the logic for converting from Markdown to Vue SFCs) to run in the browser environment. This would mean running this logic in the browser, enabling the real-time conversion of user input Markdown text into Vue components. This might require some modifications to the current code to adapt it to the browser environment.
Once this functionality is implemented, it should be possible to dynamically render the corresponding Vue components as the user inputs Markdown text.
I was wondering if you could provide some possible development approaches, as I'm interested in iterating on your code to add this feature.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I have been studying the source code of this project recently, and my understanding is that the core function of vite-plugin-md is to convert Markdown files into Vue Single File Components (SFCs) during the build phase.
However, I see a use case where we might want to dynamically convert user input Markdown text into Vue components at runtime, which would require performing the Markdown to Vue component conversion on the client side. In other words, the conversion logic needs to be moved to the browser: I am contemplating porting the core logic of this project (i.e., the logic for converting from Markdown to Vue SFCs) to run in the browser environment. This would mean running this logic in the browser, enabling the real-time conversion of user input Markdown text into Vue components. This might require some modifications to the current code to adapt it to the browser environment.
Once this functionality is implemented, it should be possible to dynamically render the corresponding Vue components as the user inputs Markdown text.
I was wondering if you could provide some possible development approaches, as I'm interested in iterating on your code to add this feature.
Thank you for your consideration.
Beta Was this translation helpful? Give feedback.
All reactions