0.0.47 • Published 19 hours ago

@axos-web-dev/shared-components v0.0.47

Weekly downloads
-
License
ISC
Repository
-
Last release
19 hours ago

Installation

Using npm:

$ npm install @axos-web-dev/shared-components

To import components In Node.js:

// Import Components
import {
  AlertBanner,
  CallToActionBar,
  DownloadTile,
  ImageBillboard,
  SecondaryFooter,
} from "@axos-web-dev/shared-components";

// Import Types/Interfaces

import { AlertBannerInterface } from "@axos-web-dev/shared-components/dist/AlertBanner/AlertBanner.interface";

In css files:

/*** Import styles ***/

@import "@axos-web-dev/shared-components/dist/assets/AlertBanner/AlertBanner.css";

Shared components

This project is develop using React + TypeScript + Vite + Storybook + Vanilla-extract to building custom components for internal use.

How to add new component

For add a new component use the src/lib folder and create a folder for the component. After that you should register an export in src/lib/main.ts file.

Also you need create a storie for the new component. Go to src/stories and create a new file or folder.

git clone bofaz@vs-ssh.visualstudio.com:v3/bofaz/Axos%20Marketing%20Cloud/Shared%20Components shared-components

cd shared-components

npm install

# for using storybook
npm run storybook

# for build
npm run build

# for testing in other projects
npm run build

npm link

For publishing we need to udpate the version we are using semantic versioning

Given a version number MAJOR.MINOR.PATCH, increment the:

    MAJOR version when you make incompatible API changes
    MINOR version when you add functionality in a backward compatible manner
    PATCH version when you make backward compatible bug fixes

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

we can update the version with the following commands:

# bumps the patch number like 0.0.0 -> 0.0.1
npm version patch

# bumps the patch number like 0.0.0 -> 0.1.0
npm version minor

# bumps the patch number like 0.0.0 -> 1.0.0
npm version major

How to publish new library version to npm

First update the version as previously described

npm version [...]

Then you will need to login into npm to do that write:

npm login --scope=@my-org

Last you to publish the new version:

npm publish
0.0.47

19 hours ago

0.0.44

5 days ago

0.0.45

5 days ago

0.0.46

5 days ago

0.0.43

12 days ago

0.0.42

13 days ago

0.0.41

15 days ago

0.0.40

18 days ago

0.0.38

19 days ago

0.0.39

19 days ago

0.0.37

20 days ago

0.0.36

20 days ago

0.0.34

21 days ago

0.0.35

21 days ago

0.0.30

25 days ago

0.0.31

25 days ago

0.0.32

25 days ago

0.0.33

25 days ago

0.0.28

25 days ago

0.0.29

25 days ago

0.0.21

28 days ago

0.0.22

27 days ago

0.0.23

27 days ago

0.0.24

27 days ago

0.0.25

26 days ago

0.0.26

26 days ago

0.0.27

26 days ago

0.0.20

29 days ago

0.0.19

1 month ago

0.0.18

1 month ago

0.0.16

1 month ago

0.0.17

1 month ago

0.0.15

1 month ago

0.0.13

1 month ago

0.0.14

1 month ago

0.0.12

1 month ago

0.0.11

2 months ago

0.0.10

2 months ago

0.0.9

2 months ago

0.0.8

2 months ago

0.0.5

2 months ago

0.0.7

2 months ago

0.0.6

2 months ago

0.0.4

2 months ago

0.0.3

2 months ago

0.0.2

2 months ago

0.0.1

2 months ago