Security News
38% of CISOs Fear They’re Not Moving Fast Enough on AI
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
@mekari/mekari-ui-vue
Advanced tools
--- General web components in Mekari. The components are made using vue.js as its framework. Styling of components on Mekari UI Vue uses [Mekari UI Toolkit](https://bitbucket.org/mid-kelola-indonesia/mekari-ui-toolkit/src/master/). Don't forget to import
General web components in Mekari. The components are made using vue.js as its framework. Styling of components on Mekari UI Vue uses Mekari UI Toolkit. Don't forget to import the styling from Mekari UI Toolkit on your application first before using components from Mekari UI Vue.
Before running the setup, make sure to fulfill the prerequisite above. After that, the repo needed to be cloned, and then run the initial setup script. Here is the snippet:
git clone git@bitbucket.org:mid-kelola-indonesia/mekari-ui-vue.git
cd mekari-ui-vue
yarn
Mekari UI Vue uses Storybook to see a preview of the components and its documentation. The preview of component can be updated dynamically using option provided from control panel.
The storybook needed to be run first in order to be able to see the preview the components on Mekari UI Vue. By default, the storybook will be run on http://localhost:6006. Here is the snippet to run storybook on Mekari UI Vue:
yarn storybook
In some case, you need the static version of storybook so you can embed it on some other pages. This can be done using build-storybook
command from storybook. The built code by default will be located in /build
directory. Here is the snippet to build storybook:
yarn build-storybook
Sometimes, the Mekari UI Vue and Mekari UI Toolkit developed at same time. Because of that, sometimes the package version of Mekari UI Toolkit used in Mekari UI Vue on storybook from npmjs will not be the same with the current Mekari UI Toolkit that is still in development. To handle this, you can use the source of Mekari UI Toolkit to use from local machine like this:
//package.json
.
.
.
"dependencies": {
"mekari-ui-toolkit": "file:/location/to/mekari-ui-toolkit",
.
.
.
},
.
.
.
After that, make sure mekari-ui-toolkit on node_modules is using the right version. You can check it on yarn.lock
. It will look like this:
//yarn.lock
.
.
.
mekari-ui-toolkit:
version "1.0.11" -> this version is based on version in package.json
resolved "/location/to/mekari-ui-toolkit"
.
.
.
Or if you really want to make sure 100% your mekari-ui-tollkit is using version from your local machine, you can run these commands on your root mekari-ui-vue directory:
rm -rf ./node_modules/@mekari/mekari-ui-toolkit
rm yarn.lock
yarn
You can read more documentation on many how to in Mekari UI Vue here.
If you want to contribute to Mekari UI, you can read this guide.
FAQs
--- General web components in Mekari. The components are made using vue.js as its framework. Styling of components on Mekari UI Vue uses [Mekari UI Toolkit](https://bitbucket.org/mid-kelola-indonesia/mekari-ui-toolkit/src/master/). Don't forget to import
We found that @mekari/mekari-ui-vue demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.