New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework docs landing page #446
Comments
I am able to build my own react component and publish it on NPM to use with IDOM. This technically means I can put a full-fledged react web app directly inside jupyter notebook with IDOM. I love this library ❤️ thank you so much. |
@rafaellichen that's great to hear! It'd be cool to learn how your using IDOM - just start a discussion and I'd be happy to chat about it. |
Closed by: 6b8119b |
this is probably a very late response 😅 but here is the template for how we used this library to make jupyter notebook widget. |
Interesting! Is there anything in idom-jupyter you felt was lacking that motivated you to create this template? I was hoping people would be able to use |
mostly minor details:
|
From what I can tell, I'm guessing that this is useful while developing the widget? If so, I think this is a feature that could be built into the core of IDOM. The idea would be to create a thin wrapper around any exported components that would, on some cadence, check to see if the source file the component originates from has been modified and trigger a re-render.
I'd be open to a contribution that would allow users of IDOM's template repo to select their preferred bundler. We could use a |
The text was updated successfully, but these errors were encountered: