npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sedoo/unidoo

v0.1.59

Published

Commons components to simplify vuetify based application developement

Downloads

68

Readme

unidoo

see Documentation

Library

For users

How to integrate Unidoo in a project

  1. Install the module
npm i @sedoo/unidoo
  1. In you main.js add the following lines
import { Unidoo, UnidooKeycloak } from "@sedoo/unidoo";
Vue.use(Unidoo, { vuetify, axios, iconfont: 'mdi' }); // à mettre après Vue.use(VueAxios, axios);
Vue.use(UnidooKeycloak, { axios }); // à mettre après Vue.use(VueAxios, axios);

NB :

  • Unidoo : bibliothèque de composants vuetify
  • UnidooKeycloak : wrapper keycloak

For developers

Warning

Naming convention: the main branch is called main and not master

How to publish the library in NPM ?

The publishing of the library is automated by the Gitlab pipeline. No other method should be used.

Gitlab pipeline is triggering after each git push --tags on the main branch :

  • the documentation of the library is built and deployed as a gitlab page
  • the library is built and deployed to @sedoo/unidoo npm registry

If the build is successful, the system will publish it on NPM using the version number indicated in the package.json file. If this version corresponds to an already published version, the build will stop here. Else, the version is published.

Hence, to publish an new version, it is important to update the number in the package.json file.

Tips to prevent errors in the publishing process in the pipeline:

  • use the npm run build --fix command to test the build locally before pushing the code to the repository and fix the linting errors
  • use the npm run docs:build command to test the documentation build locally before pushing the code to the repository Nevertheless if the pipeline fails, check the logs in the Gitlab pipeline console to find the error : Example of error : error Unexpected console statement no-console means that there is a console.log() statement in the code. Resolve action : Remove console.log. However if log are necessary a workaround can be to implement infoLog() and errorLog() functions in the code of the component (like in the UnidooMapGeoFeatures) to replace console.log() and console.error() statements.

Then run the demo locally like bellow to check that everything is ok before merging and pushing the code on the main branch of the repository:

Demo application

On developement station

To run the demo locally:

npm run docs:dev

Demonstration on the Web in Wordpress after publishing

Live demonstration