Wicara 0.8 - "Chell"
Welcome to Wicara 0.8! This new release sees various major changes as a foundation to help shape the future of Wicara past this minor release.
Installation
Wicara 0.8 requires styled-components
v4+. First, install the next
version of the core Wicara package and styled-components
.
# yarn
$ yarn add styled-components @wicara/core@next
# npm
$ npm install --save styled-components @wicara/core@next
Then, you will need to apply the style resets + theme provider. Wrap your app inside the WicaraProvider
to use the resets and ThemeProvider
component provided by Wicara.
import { WicaraProvider } from '@wicara/core';
export default function MyApp({ children }) {
return <WicaraProvider>{children}</WicaraProvider>;
}
New features
Rewritten from the ground up
Wicara now uses styled-components
, with styled-system
as a method to build composable components using primitive props. Check them out!
New foundational components
Added several foundational components for improved flexibility and composability. See this storybook page for guides.
Simplified npm package structure
The architecture of Wicara 0.7 is based off of single npm packages per component. We quickly realised that this was a bad idea. So, we decided to merge them all into a single package, @wicara/core
. Code-splitting is still available since we still publish an ES Module version of the package.
We've also provided the font stack we use on a separate package, @wicara/fonts
.
New documentation URL
The documentation for Wicara has been migrated from Netlify to ZEIT Now. The new documentation URL can be found at wicara.now.sh. You can now open the "Notes" tab on each component story for guides on the corresponding component.
You can also read the README for detailed installation + usage guides.
Migration guide
To provide a smooth transition from Wicara 0.7, we provided the following migration guidelines. Please read if carefully when migrating your projects to Wicara 0.8.
We'd love your help!
Wicara is open source, which means it's also developed by the help of developers like you! Read our Contributing Guidelines to get started.