0.0.65 • Published 4 months ago

@formant/ui-sdk v0.0.65

Weekly downloads
-
License
MIT
Repository
github
Last release
4 months ago

UI SDK

A library of UI components from Formant. These components are re-exported subset of mui. You get the best of all worlds:

  • components that look beautiful and fit in within a custom view/module.
  • high quality industry standard component system for React (i.e. your knowledge is re-usable for other projects that aren't Formant related).
  • unique formant specific components not offered by mui

demo

Unique Formant components

  • Timeline scrubber - COMING SOON

Other MUI components

You can use the whole suite of components from mui that will inherent our styles. The components that are explicitly tested from this packages have styling that is known to be of high quality.

Setting up in your own project

yarn add @formant/ui-sdk

or check out our ViteJS example

Font

Formant UI Sdk uses the Inter open source font, add this to your project

<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link
  href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap"
  rel="stylesheet"
/>

Formant React hooks

Within this project are a number of hooks that make access informationa about your fleet easy to do.

Developing on ui-sdk

yarn
yarn dev

Running storybook

yarn storybook

Building for production

Weirdly, typescript requires npm layout package in order to generate its types

Deploying a new version

# use npm to bump the version number
npm version X.Y.Z 

# add all the changed files from the preversion/postversion tasks
git add .

# commit all the changes with a uniform commit message
git commit -m ui-sdk@$(node -p "require('./package.json').version")

# add a unified annotated tag for this version
git tag -a release/ui-sdk/$(node -p "require('./package.json').version") -m ui-sdk@$(node -p "require('./package.json').version")

# publish this version to npm; use "--tag=next" for future releases
npm publish

# push everything to remote vcs with the tags
git push --follow-tags

should run all that's necessary for creating a build

0.0.65

4 months ago

0.0.62

9 months ago

0.0.63

9 months ago

0.0.64

8 months ago

0.0.61

9 months ago

0.0.60

11 months ago

0.0.59

11 months ago

0.0.55

11 months ago

0.0.56

11 months ago

0.0.57

11 months ago

0.0.58

11 months ago

0.0.51

1 year ago

0.0.52

1 year ago

0.0.53

12 months ago

0.0.54

12 months ago

0.0.50

1 year ago

0.0.48

1 year ago

0.0.49

1 year ago

0.0.46

1 year ago

0.0.47

1 year ago

0.0.45

1 year ago

0.0.44

1 year ago

0.0.41

1 year ago

0.0.42

1 year ago

0.0.43

1 year ago

0.0.40

1 year ago

0.0.37

1 year ago

0.0.38

1 year ago

0.0.39

1 year ago

0.0.31

1 year ago

0.0.32

1 year ago

0.0.33

1 year ago

0.0.34

1 year ago

0.0.35

1 year ago

0.0.36

1 year ago

0.0.30

1 year ago

0.0.27

2 years ago

0.0.28

1 year ago

0.0.29

1 year ago

0.0.24

2 years ago

0.0.25

2 years ago

0.0.26

2 years ago

0.0.20

2 years ago

0.0.21

2 years ago

0.0.22

2 years ago

0.0.23

2 years ago

0.0.18

2 years ago

0.0.19

2 years ago

0.0.10

2 years ago

0.0.11

2 years ago

0.0.12

2 years ago

0.0.13

2 years ago

0.0.14

2 years ago

0.0.3

2 years ago

0.0.2

2 years ago

0.0.15

2 years ago

0.0.9

2 years ago

0.0.16

2 years ago

0.0.8

2 years ago

0.0.17

2 years ago

0.0.5

2 years ago

0.0.4

2 years ago

0.0.7

2 years ago

0.0.6

2 years ago

0.0.1

2 years ago

0.0.0

2 years ago