-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
NPM Module #160
Comments
That's an interesting idea. What do you think about that? |
To be a little more specific, I'm building an electron app that already uses Material UI and has its own theme defined. It would play very well with something like Signal, especially considering Signal renders well at most sizes. That being said, it can pose an interesting opportunity to expose APIs for controlling things like key bindings and events like const [project, setProject] = useState<SignalProject>()
<Signal value={project} onChange={setProject} /> At the end of the day, I suppose what I'm looking for is an export that does not include Sentry and simply exports the |
If you're interested, what I think would be a good first step is looking into GitHub actions that can run a build on push to master and publish to NPM. |
Any thoughts on exposing the midi editor in Signal as a standalone component, @ryohey? |
Is your feature request related to a problem? Please describe.
I'm building a music project editor and would love to include Signal as an editor within the page.
Describe the solution you'd like
import { Signal } from 'signal-react'
Additional context
This would require publishing on NPM and including a bundle that doesn't include things like Sentry.
The text was updated successfully, but these errors were encountered: