JSPM

@orfium/ictinus

2.18.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1648
  • Score
    100M100P100Q126908F
  • License MIT

Package Exports

  • @orfium/ictinus

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@orfium/ictinus) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Ictinus

A React UI kit library with custom components that fits Orfium products internally.


npm pan

📦 Installation

$ npm install @orfium/ictinus
$ yarn add @orfium/ictinus

if you want the next version you can always use the next tag. Remember: this is a release candidate, we encourage you to lock version on installation to avoid any changes

$ yarn add @orfium/ictinus@next

🔨 Usage

  1. Start by wrapping your App with ictinus ThemeProvider component like below
import { ThemeProvider } from '@orfium/ictinus';

const App = () => (
  <ThemeProvider>
    <Router>...</Router>
  </ThemeProvider>
);
  1. That's it, now you are ready to go.
import { Select, Button } from '@orfium/ictinus';

✨ Extra

Theme usage

Now you can can have access to the library's theme config by using the hook provided

import { useTheme } from '@orfium/ictinus';

const theme = useTheme();

Theme config

You can apply your own branded colours for each product at the definition of the ThemeProvider. This way you can have access everywhere.

<ThemeProvider
    theme={{
        palette: {
            branded1: theme.colors.orange,
            branded2: theme.colors.ciel,
        },
    }}
>
    ...
</ThemeProvider>

Emotion Project - Merge theme configs from different providers

If you are already using emotion and you have defined a different provider you still have to define Ictinus ThemeProvider as well. You must put the theme config example at the top of the providers and yours afterwards.

Then you must use the below function to create a new theme config for the second provider

export const defaultTheme = (ancestorTheme: IctinusTheme) => ({
  ...ancestorTheme,
  ...theme,
});

The final outcome will look like this.

<IctinusThemeProvider
  theme={{
    palette: {
      branded1: theme.colors.orange,
      branded2: theme.colors.ciel,
    },
  }}
>
  <ThemeProvider theme={defaultTheme}>
    ....
  </ThemeProvider>
</IctinusThemeProvider>