x-locations/ui-components

https://xl-ui-components.vercel.app/

Development tips

If you want to use this repo in as a dependency in another repo but unsure yet of your changes, you can add it as a dependency like this:

``sh
"@x-locations/ui-components": "git+https://:x-oauth-basic@github.com/x-locations/ui-components.git#"
"@x-locations/ui-components": "git+https://:x-oauth-basic@github.com/x-locations/ui-components.git#"
`

Important Note:

Since this repo is private, you must setup your Personal Access Token (PAT). You can follow this setup:
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token

$3

This repository follows commitlint config so make sure to follow the rules.

- For new features, add prefix feat:
- For bug fixes, add prefix fix:
- For refactors, add prefix refactor:
- For docs, add prefix docs:

Examples:

Correct

`sh
feat: some message
fix: some message
refactor: some message
docs: some message
`

Incorrect

`sh
: some message
foo: some message
feat: some message.
fix: some message that is way too long and breaks the line max-length by several characters
`

Important Note:

Make sure prefix is in lowercase, and does not end in a dot .
Keep it short and simple

More details: @commitlint/config-conventional

Publishing a beta version to npm

Important!
Make sure you are in the branch you want to publish.

Choose a version.
In this example, I am using 2.0.0-beta.0.

`sh
npm version 2.0.0-beta.0
`

Login to your npm account.

`sh
npm login
`

After this command, you will be prompted to open it in the browser. If you're already logged in, you may be prompted with the OTP.

After logging in, you can now publish.

`sh
npm publish --tag beta
`

Check if you have successfully made the beta version in the npm package.
https://www.npmjs.com/package/@x-locations/ui-components?activeTab=versions

Remove --tag beta` if you want it to be published normally.