Just One Perfect Interface
If you want to install jopi.js
in your proyect, you should read the package installation guide.
If you want to work on jopi.js
you should install the dependencies and then start the development server.
For yarn
:
$ cd jopi.js
$ yarn
$ yarn run dev
For npm
:
$ cd jopi.js
$ npm (i | install) # Use one of these options
$ npm run dev
- Storybook (for building isolated components)
- React
- Styled-components (CSS-in-JS)
- Styled-system (Style props for rapid UI development)
- Lerna.js (monorepo and tool for publish packages used in CI)
- Framer Motion (animations)
- STRUCTURE: Upgrade dependencies (Framer Motion)
- STRUCTURE: Upgrade dependencies (storybook 5.3)
- DOCS: Improve documentation of the packages.
(*) Today, every visual element is a package in npm. Maybe we should group them by elements (forms, core, extra, theme, hooks)
- PACKAGES: Carousel.
- PACKAGES: Textarea - restyling.
- PACKAGES: Alert - restyling.
- PACKAGES: Box - restyling.
- PACKAGES: List - restyling.
- PACKAGES: Paginator - restyling.
- PACKAGES: Label - restyling.
- PACKAGES: Table filter.
You can check how to theming and follow the theme specification.
Yes you can, we are using it. The only extra thing that you need to do is crate a declarations.d.ts file on your project and declare jopi.js packages that you would like to use. Like:
declare module '@oneloop/jopijs'
declare module '@oneloop/theme'
declare module '@oneloop/hooks'
For this proccess we use lerna cli. Basically, we use 2 commands to achieve the goal.
lerna version
To generate new versions of the modified packages.
Maybe, sometimes, we need to use the --force-publish
option of the command to force the generation of new versions.
lerna publish
Publish packages that have changed since the last release. Here we have 2 options for publish.
from-package
: explicitly publish packages where the latest version is not present in the registry.
from-git
: Explicitly publish packages tagged in the current commit
For more info check lerna docs.