-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Blaze standalone #290
Comments
So we are waiting for MDG to move some of core packages Blaze depends on to NPM. Only after that Blaze can move. But I have not seen any activity about that in quite some time. |
That's a shame, ok, thanks for the update @mitar I'll check back again later |
Is there any update for making Blaze standalone? |
@camstuart @anomepani I ported to npm here: https://www.npmjs.com/package/meteor-blaze-runtime it works nicely, but it does depend on a bunch of (potentially out of date) packages that people have extracted from meteor to npm by hand |
+1 |
I'm closing this issue because it's too old. If you think this issue is still relevant please open a new one. Why? We need to pay attention to all the open items so we should keep opened only items where people are involved. |
The website still mentions that blaze will one day be a standalone UI. Is this still planned?
I have tried all the major UI libraries and frameworks, and never been as productive as I was in blaze.
If it's not happening, or a long way off, can you suggest an alternative that works in a similar way?
The text was updated successfully, but these errors were encountered: