-
Notifications
You must be signed in to change notification settings - Fork 13
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
Flame next major #49
Comments
4 tasks
FlameTheme should not be removed. It should be FlameFonts |
My bad, updated 😄 |
Flame 2 released, see #99 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Tracking issue on what's coming for the next major version of Flame packages.
@lightspeed/flame
Deprecated
FlameFonts
component from@lightspeed/flame/Core
will be removed. Instead, use the link tag to load fonts. Problem is Next.jsHead
component does not play nice with it and actually removes thelink
after client-side takes over. Fonts won't be changing very frequently so its usefulness is very limited.Group
will either be moved to a separate package@lightspeed/flame-group
or remain undocumented but kept as an hidden feature in the codebase. See Rework Group and Inputs #2.@lightspeed/flame-tokens
Deprecated
cr-
namespace will be removed in favour of thefl-
namespace. See Output new tokens to new directory. Output new and legacy namespaces #56.The text was updated successfully, but these errors were encountered: