You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well and some of the stylesheet stuff is leftovers from me trying to customize the theme. Which idk with how I've been out of the loop if anyone picked up on and finished that work. And there's the possibility of switching frameworks to one with less warts to work around too that I may start a branch/pr for.
Well and some of the stylesheet stuff is leftovers from me trying to customize the theme. Which idk with how I've been out of the loop if anyone picked up on and finished that work. And there's the possibility of switching frameworks to one with less warts to work around too that I may start a branch/pr for.
Well and some of the stylesheet stuff is leftovers from me trying to customize the theme. Which idk with how I've been out of the loop if anyone picked up on and finished that work. And there's the possibility of switching frameworks to one with less warts to work around too that I may start a branch/pr for.
Yeah this is in relation to our docs on this subject, rather than those files existing for this repo. Sorry if it was unclear
Have you checked for existing feature requests?
Summary
Our docs have a section that goes over special keys in a
package.json
here, but it seems some fields that we accept aren't documented anywhere.Such as
styleSheets
andmainStyleSheet
. Good reference here.What benefits does this feature provide?
Better Docs
Any alternatives?
Leaving as is, where it nearly includes everything.
Other examples:
No response
The text was updated successfully, but these errors were encountered: