-
Notifications
You must be signed in to change notification settings - Fork 4
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
Make it work with preact #50
Comments
What part of kremling doesn't work, if you use preact-compat and alias |
Yeah, |
What could kremling do differently to make it work with both? The library has to do Potentially we could publish the src directory and remove all references to react from it - attempting to auto-inject the imports during build? Then you could use the published src directory and compile it with a different jsx pragma for preact?? I'm not sure if that would make sense - would gladly take direction from other projects that have done this. |
I've actually been thinking about this lately - the core of kremling could be framework agnostic: on component mount, append css - on component unmount, remove css seems like we could pull the core of kremling out and make framework-specific implementations (like how you guys did it with single-spa) might be able to keep it all in the same package and force consumers to choose their framework:
|
or make several packages: |
This is a case where monorepos are useful :) Maybe if I get time, I'll put together a mono repo implementation |
started working on a mono repo, and thought it would be fun to implement kremling inside crankjs so I started there 😄 repo: https://github.com/geoctrl/kremling-monorepo this is just an idea - I'm open to ideas - currently includes 3 packages:
adding |
don't hate me, but I agree with this. I feel like libraries are a good case for monorepos. |
It would be great to make kremling work with preact
The text was updated successfully, but these errors were encountered: