@nuskin/product-components-vue

"Product domain vue components are organized here.",

Installing

Usng npm:

npm add @nuskin/product-components-vue

Usng yarn:

yarn add @nuskin/product-components-vue

Example usage

import {ProductCard} = from '@nuskin/product-components-vue';

Storybook

Use Node v14.21.2 to ensure successful use of yarn sb script.

Local Development

In order to test changes of this library locally you can simply test your changes in storybook, and once storybook reflects the changes you want, you can create a new release version and install the new release version in the client application that is receiving the product-components-vue library.

If you want to test your local product-components-vue changes in the local version of your client application that is recieving those changes before you build a release, follow these steps:

1. Inside product-components-vue working directory, make the changes you want to make, save the files, and run yarn link. This will create a local version of the product-components-vue package.
2. Go to the client application working directory and remove the "@nuskin/product-components-vue" from the package.json. Remove node_modules and re-run yarn install. We need to do this first because the npm released package and the local package can get confused.
3. Still inside your client app, run yarn link @nuskin/product-components-vue.
4. You should now be able to import any component from @nuskin/product-components-vue inside your client application, and it will be pulling from your local version that you linked earlier.
5. You will need to restart your client app each time you change your local product-components-vue changes.
6. Once your satisfied with your changes, you can run yarn unlink and re-introduce the released version in your client apps package.json (@nuskin/product-components-vue).

Resources

• Testing vue-cli-service
• Storybook Vue
• Sonar

License

MIT